In Development database, I have granted CREATE STORED PROC permission to all of our Developers. When they create SP, I compile their SPs as dbo. Then I grant Exec permission so that Developers can execute each other’s SP. This saves me from granting permission to each of the underlying objects–table, view, etc. through ownership chaining. It adds extra step for developers who have to come to me to compile their SPs, otherwise they run into broken ownership chain issue. If I make them database owner to the database, I fear that they may accidentally delete each other’s SPs. How do I solve this problem?
by Ari Weil
You should take advantage of security groups if you want to keep your current arrangement; add the developers to a single group and simply maintain the group’s authorities.
Still, I should think Database Snapshots are perfect for your situation. A snapshot is a static, read-only view of a database. You can have the developers create their procedures on the snapshot, evaluate the code, then create it on the source database. The developers can have full access to the snapshot database, while you maintain restricted permissions on the source (real) database. Read more <a href=”http://msdn2.microsoft.com/en-us/library/ms190467.aspx”>here</a>.
Tags: Programming
Share this post with friends
