I'm really new to MSDE so I just want to know...Is SQL Server 2000 a prerequisite for MSDE particularly for developers? If yes, then is it(SQL Server 2000) a prerequisite for clients?
The thing is, I can't find a tool where I can create databases after installing MSDE...the only way I can think of is also installing SQL Server 2000 and create the database from there...
Hi,
I've just released Nautilus v1.0.6. I would apreciatte your opinion and comments.
With Nautilus you can:
-search tables without tipying the exact name.
-browse records, filter and locate records
-"Pivot" records to see it's related records (folowing the Foreign keys).
-Generate scripts: create table, insert into, delete, update.
-Build dynamic diagrams.
and many more features.
http://sourceforge.net/projects/nautilus/
Thanks, Marcos.
OMNI GROUPJoin Bytes!T-SQL/ CONTRACT TO PERM/ ATLANTAI'm looking for 1-2 TSQL developers for a 4 month contract to hirerole in Atlanta, GA. Ideally the candidate would be local or regional and aUS Citizen with 2-4 years of Microsoft TSQL development experience.Salary in the $55,000--$60,000 or so. annual range. Contract rate would beApproximately $36 hr W2 or 39hr 1099. One is responsible for their ownexpenses.Once perm, the company offers full benefits.If interested and qualified, answer the six questions below. EmailanswersWITH a resume to: Join Bytes!1. TSQL experience-------------------yrs2. MS SQL experience---------------yrs3. OO Languages----------------------4. Citizenship Status------------------5. Availability--------------------------6. Contract Rate ---------------pr hr..
View 1 Replies View Relatedwhere can i find pay rates or salaries for ssis developers?
thanks in advance.
New to SQL so please be patient. I'd like to give my developers "See All/Do Nothing" rights to my production server. I want them be able to see everyting that I do, as SA, but not be able to change anything. Is this possible?
Thanks for the help...Art
I will have a group of developers creating objects in a database. Currently they all
create them with the SA account. I would like to have them mapped to the dbo or some method
that when they create objects all objects are dbo.object name and not h1fed99.object name.
Is there a good methor or practice to handle this
I'm currently trying to obtain an aggregate function from a table to provide a cumulative monthly value. I would like to create a view to obtian this from the underlying table i.e month=1 ,month=1,2 , month=1,2,3 Etc.
month sales
1 10
2 0
3 20
month cummulative_sales
1 10
2 10
3 30
Anyone got any ideas ???
Always looking for people who are strong with microsoft technology for new oppurtunities in the Seattle area. If you are good, we can help you find your ideal next position.
don't be shy. shoot me an e-mail.
thanks
Pat Copeland
Hey,
I am looking for mid to senior level SQL developers for some sweet companies here in Seattle. A chance to work in a dynamic envirnoment with bleeding edge Microsoft technologies. Are you good? then we can help.
shoot me an e-mail.
patc@snowdogs.com
thanks
pat copeland
snowdogs
we are for the people.
I am looking for strong SQL developers and/or DBA's for some really sweet companies here in Seattle. Anyone interested that is good and wants to hear about new oppurtunities? I would love to help you out.
don't be shy just shoot me an e-mail.
This may be an intuitively obvious question, and if so, I apologize.
Speaking in terms of best practices here, what is the preferred method for allowing developers to work with databases in SQL Server? If they use Management Studio, then they have access to tools for perhaps messing with other databases, etc. that they should not (assuming it is not correctly secured). Likewise with Enterprise Manager. I can see where they would use Query Analyzer, but these two are now combined in Management Studio.
I'm just inquiring into how other DBA's do this. I realize there are DBA's that are developers and vice-versa, but what if there is a clear line of distinction and you want to keep the tools used in these roles separate?
Thanks in advance.
Kevin
Are you new to SQL Server 2005? http://aspalliance.com/1455 These are the frequently asked questions in SQL Server 2005. Let me know your comments.
Uday Denduluri
Software Engineer
Refer my articles at http://aspalliance.com/author.aspx?uId=62740
Hi,I have just started a business and I was wondering if I could get someadvice about product selection. I am currently buiding my websiteusing asp.net connecting to sql server database.My question: Am I only required to purchase a SQL Server DevelopersLicence? I won't be hosting the site so I think this is correct butthought I should check.Cheers,Jack
View 1 Replies View RelatedI just bought a copy of SQL Server 2000 (with service pack 3a) that Iintended to install and run on XP Pro. My concern is that the requirementslist on the box do not include XP or XP Pro. Will SQL Server 2000 developeredition run on XP Pro?
View 3 Replies View RelatedHi Everyone,
Were looking from some feedback, thoughts, comments, suggestions on a permissions issue in our SQL Server 2005 environment. We have a Development (stand-alone server) and Production (activepassive cluster). Both running SP2. We're looking for the best way to manage permissions for the developers without giving them dbo privileges.
As background information, here's a note / response from a developer outlining the permission they need.
-----------------------------------------
"Our team needs enough permissions on DB database to:
Create and modify DB object such as tables, stored procedures, keys, triggers, views, ...
Be able to execute stored procedures and other basic DB objects
One of the issue I had when working on DatabaseA which was never resolved was that I could create tables, but had no rights to modify them once created.
I could modify them via scripts, but not via graphical interface which is a pain.
I think we should have full permissions to dev DB other than to drop DB, and modify system DB settings.
So that we can work within the created DB shell completely."
-----------------------------------------
Previous to supporting the current SQL Server 2005 environment, the developersapp owners had db_owner for their databases. Definitely not a best practice as with 2005 db_owner is ablke to delete databases. Moving away from this, we thought we would scale them back and only grant them the following database roles:
db_datareader
db_datawriter
db_ddladmin
With these roles, they were able to create the tables, views, stored procedures, etc...... but problems arose when they tried to modify the objects they created as well as execute stored procedures. It's going to be a pain to grant permissions on each stored procedure. More of a mystery is allowing them to make design changes within Studio Manager. Given they can already do this using scripts but not the GUI.
So there is an issue with using GUI tools to design the tables.
Here's a thread we found that tries to explain the reason why they can't use the GUI to make design changes.
Even if you have CREATE TABLE permission, there are limitations to the modifications you can make. Remember, as you modify an existing table or design a new one, your work can induce attendant modifications in other tables. For example, if you change the data type of a foreign-key column, the corresponding column in the primary-key table will be automatically modified by the Visual Database Tools. If you do not own the primary-key table, and you are not logged in as the system administrator, database owner, or a user that is a member of the db_owner role, your modification will fail.
When we created the accounts, we assigned the default schema to be 'dbo'. This was thought to simplify administration of the objects. In SQL Server 2000, this was a best practice. Now, in SQL Server 2005, they changed everything with the user schema separation.
So we have a developer (devuser) - created with default schema (dbo). Any object that are being created are owned by dbo. (ie... dbo.table1, dbo.storedproc1, etc..) So dbo owns the objects, not the user.
Does anyone have any ideas? Do we create a new schema and assign permissions? Do we create a new fixed database role for the developers? I'm curious as to how others are assigning permissions to developers on development and production servers.
Thanks,
Rob
What is the best practice in managing an SSIS development with multiple developers.
For example, we have 2 guys that will be developing various SSIS packages for a common data warehouse. We are most likely going to divide up the unit of work by the tables that need to get loaded. So, one guy will develop packages to load tables 1 thru 5 and the other guy will develop packages to load tables 6 thru 10.
Should each person work within his own project? (Not sure what a difference between a solution and a project is, so I may be thinking of a solution.) If so, can multiple people open the same project? I don't think you can.
I'm very new to SSIS and this would be the first time I'm doing something like this. I haven't even deployed a package to the server yet so I'm not even sure what implications/consideration I have before I take on this development effort I'm about to.
Does SQL Server 2005 Developers Edition come with Visual Studio Pro 2008? I know it did with Visual Studio Pro 2005.
If not, if I purchase SQL Server 2005 Developers Edition, can I install on the same machine as VS Pro 2008?
Will there be a Developer's edition to SQL Server 2008?
I realize I can't put databases I build into production with just the developer edition.
thanks
james
Is it possible to use SQL express to create a web application that is developed by more than one user? It seems to be registered on the <machinename>/SQLEXPRESS but the ASP.NET tool in visual studio seems to always want to create a sql express version in its app_data folder.
How can i set up a database such that 2 or more people can use that for developing the application. No doubt that SQL express with be suitable eventually, but initially we need to access the same database for development, but be on multiple machines. Can this be done, if so how?
Hi,
I have problems with the concept of user-defined messages.
I'm migrating from sybase ase to sql2005 and found out that there is only one global pool of messages.
Do you give every project on this server a dedicated range of error-numbers?
Another problem: only the sysadmin oder serveradmin can call sp_addmessage.
In my environment the developers own their databases and used to be able to create their own messages.
Now I try to let the developers call sp_addmessage by calling a "wrapper-procedure" which gets the needed rights.
create procedure sp__addmessage(@msgnum int, @severity smallint, @msgtext nvarchar(510), @lang sysname )WITH execute as OWNERASselect 'I am ' + suser_name(), user_name()exec sp_addmessage @msgnum, @severity, @msgtext, @lang gogrant execute sp__admessage to testusergo
When executing it as normal user (without sysadmin/serveradmin-roles) the output is:
I am sa dboMsg 15247, Level 16, State 1, Procedure sp_addmessage, Line 18User does not have permission to perform this action.
Isn't it strange?
Do you have a different idea how users/developers can create messages?
Thx
I like to get a feedback from other DBA's out there, I have a user with a consultant that need's Enterprise Manager installed on the user's desktop
in order for them to develop code for the user.
Is the above a good reason to give out to the user the Enterprise Manager
tools?
Please give me what is acceptable tools for the user/consultan.
Thank you
Jorge
Hello -
I am looking for a way to allow users to create and edit their own stored procedures, saved under DBO (not under their own schema).
Any help would be greatly appreciated!
Paul
Hello,
since Sqlserver 7.0 looked so easy to our developers, they would like to perform
development and administator tasks. Our environment will begin with 3 development
groups, each with about 1-4 developers per group. We're might reach about 10-15 dbs
with in a year. Most of the databases will be under 1 Gig(may be under 500 MB) and may be
couple 2 Gig Dbs. We're not sure how many more databases we'll have.
I would appreciate your opinion on this.
Thanks in advance,
yi
Hello Everyone,
I need your input. When, if ever, should programmers be given the 'sa' login. The reason that I ask is because a group of three developers have approached me asking for the 'sa' login so they could write stored procedures and do some database level tasks. I am relatively new to data admin and I am under the opinion that I should probably just alias their login to 'dbo' on the one database that they are developing their app for.
What do you guys think about this.
Thanks in Advance,
Terry
I detached a SLQ 2000 database and reattached it in 2005 Developers.When I try to access the Diagrams, the below message is received. Mydomain account is owner. I'm local Admin on my machine. Shouldn't bea problem right? How do I add the Database Diagram Support Objects?TITLE: Microsoft SQL Server Management Studio------------------------------Database diagram support objects cannot be installed because thisdatabase does not have a valid owner. To continue, first use the Filespage of the Database Properties dialog box or the ALTER AUTHORIZATIONstatement to set the database owner to a valid login, then add thedatabase diagram support objects.------------------------------BUTTONS:OK------------------------------
View 1 Replies View RelatedHow do I add a previously-made SQL Compact Edition database to my Visual Basic.Net 2005 project inside Visual Studio, and ensure that it gets built into the ClickOnce-deployed solution? Our dba has completed the db design for our project, and I need to add the file to the project I am writing business logic for.
View 5 Replies View RelatedI have read a number of threads in this forum concerning SSIS packages and Protection Level. I regret to say that I did not manage to find one that covers the problem I am experiencing.
I have saved a package that contains a SQL Server Authentication login and password. In Properties for the Package I have set
ProtectionLevel = EncryptSensitiveWithPassword
I then save my Package and use F5 to run it in Visual Studio 2005 Team Edition. It runs just fine.
I then walk over to a co-worker's desk, have him "Get Latest Version" in Source Control Explorer, and then have him double-click on the SSIS Package. It indicates that he must enter the password, which we do, and then it begins validation of the package. By changing to EncryptSensitiveWithPassword (instead of EncryptSensitiveWithUserKey) many of the earlier error messages went away.
We still get one fatal error, though, which prevents him from pressing F5 to run the package on his PC. The error message is one reported in some other threads in this forum:
Error loading PackageName(C2097).dtsx: Failed to decrypt protected XML node "DTSassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
Naturally we are running this on a computer different from the one on which the package was created/last-saved, and running with a different Windows user.
The package is a fairly simple one: it merely copies a few dozen tables from Access to SQL Server 2005 on a central server.
Might the error message be related to the Access connection? (He has the same rights to the Access database that I do, but those are based on Windows Authentication -- which makes me wonder if that might be the problem. The Access database is located on a central server, and the access rights are controlled through User Groups in the Windows File System.)
I would like for others to be able to run this and other SSIS packages I have developed.
Ultimately we would like to store completed SSIS packages in the File System (rather than in SQL Server 2005), and allow anyone in our team, who knows the password(s) for the packages, to run them without difficulty.
Is this possible?
Dan
Just getting started with mssql . . .
running mssql 2005 developers edition and will be using dreamweaver to develop sites . . . mssql documention states that the developers edition doesn't support remote access - does that mean that I have to have dreamweaver running on the same computer?
thanks,
elvis
I have some developers who would like to debug t-sql in vs2005. One developer is a sysadmin and it works fine - this is the microsoft recommended solution . This one developer can have sysadmin, but the others cannot. I read a blog post from a sql server team developer that you can grant execute to master.dbo.sp_enable_sql_debug extended sp. We could possibly grant execute of this sp if it lets developers debug in development. We do know that they could maliciously elevate priv's to SA, but that is not so much of a concern, just that they cannot easily perform sa actions.
http://blogs.msdn.com/sqlclr/archive/2006/07/07/659332.aspx - has most of the information I've gotten about this topic. From the article I can't really tell if the user has to be sysadmin to execute the sp_enable_sql_debug - even if granted. From the behavior below, I'm guessing it does.
Do I need to do something else here? Are we taking the wrong approach?
Thanks!
My commands and results -
grant execute on sys.sp_enable_sql_debug to [samtest]
go
execute as login = 'samtest'
go
master.dbo.[sp_enable_sql_debug]
Msg 229, Level 14, State 5, Procedure sp_enable_sql_debug, Line 1
EXECUTE permission denied on object 'sp_enable_sql_debug', database 'mssqlsystemresource', schema 'sys'.
Does the SQL2K Developers Edition allow you to install/test/support multi instances?
View 1 Replies View RelatedDoes the SQL2K Developers Edition allow you to install/test/support multi instances?
View 1 Replies View RelatedI have my SQL 7.0 server set for Mixed security. I see now (finally)the advantages of having windows authentication security for windowsgroups.I do most of my developing in Access Projects which require a login ofsome type. I have been using my SQL login to develop with SQL andthen when I give it to the user, I set the project to use Windowsauthentication. I want to be able to have Windows authentication onmy domain account but the user name for my windows account is the sameas my SQL account and it won't let me change the existing account.Now what happens is after I develop the product I have to have theuser login and go in and change to windows authentication. It won'tlet me do it with my sql account.I fear that if I delete my sql account and create a windowsauthentication account all the views, sps, etc. that I have createdwill still have the reference to the sql login and therefore not work.Do I need to have a generic sql account for developing? One thought Ihad was to create a new domain account so I can create that windowslogin and at least get my most recent projects working like I want to?Hope this makes sense to someone.Thanks in advance for your time.Sherry
View 1 Replies View RelatedI have both VSTS 2005 for Developers and VSTS 2005 for Database Professionals installed on my PC. I can't find any BI or SSIS projects in File->New Projects. The only database-related projects are to write Stored Procedures, Views, etc. Where is it? Did they break it when they added the Database version on top of the Developers version?
View 12 Replies View RelatedI have downloaded SQLServer2005SP2-KB921896-x86-ENU.exe and attempted to update to SP2 with no success.
SQL Server 2005 Developers Edition is installed on my computer as part of a Visual Studio 2005 installation.
When I try to run this package under my admin account, I get through the Feature Selection (selecting everything) to Authentication.
When I press the Test button or the Next button, I get "Your account information could not be verified. Press Ok to return to Authentication Mode screen to determine the reason for failure. For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator."
The Authentication screen shows "Database Services, MSSQLSERVER, Windows, domainusername, Service Failed to Start"
I am a novice SQL Server user, Clearly I am floundering! Any observations, advice, or suggestions would be greatly appreciated.