SQL SECURITY

[Guest_imported]

I am learning/running/developing an SQL 2000 Server. I have one employee who is writing the stored procedures and creating all of the tables, ect. He currently has permissions to datareader and datawriter. Our issue is that every time he creates a new stored procedure, he maintains ownership under his account "NAME/Domain Name"(before setting up his system we added 50+ stored procedures under the dbo account). When trying to execute these from any of the other machines in our workplace we get an error message stating that the stored procedure cannot be found. If we then go and manually change the ownership back to the dbo account the SP runs fine. I would like to know either how to stop his account from taking ownership, or to know how to allow our users to execute the stored procedures from both owners. Any suggestions??

 

[fluteplr]

Well the simplest thing is to make him a DBO equivalent. You can do this in enterprise manager under user security.

 

[tlbroadbent]

If you don't want the developer to be an Owner, check my response to your question in the SQL Server forum - thread183-282877. Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.