January 18, 2013 at 6:05 pm
How to create a policy that prevents users to create user objects in master database?
Thanks
January 18, 2013 at 6:17 pm
Not so much as a policy, but that could be handled with a DDL trigger.
January 19, 2013 at 6:47 am
January 20, 2013 at 5:26 pm
The thing I found on a dev server, the database developer has all the rights on the box
and when he runs the build script sometimes, it accidently goes to the master database.
One way is in the build script to add : Use userdatabase statement, then run the script, but I want also to avoid the accidental creation to master db.
January 20, 2013 at 5:41 pm
sqlfriends (1/20/2013)
The thing I found on a dev server, the database developer has all the rights on the boxand when he runs the build script sometimes, it accidently goes to the master database.
One way is in the build script to add : Use userdatabase statement, then run the script, but I want also to avoid the accidental creation to master db.
The other is to create a DDL trigger that will prevent it as well. I think this is more viable than a policy.
January 21, 2013 at 4:43 am
sqlfriends (1/20/2013)
The thing I found on a dev server, the database developer has all the rights on the boxand when he runs the build script sometimes, it accidently goes to the master database.
One way is in the build script to add : Use userdatabase statement, then run the script, but I want also to avoid the accidental creation to master db.
Set default database for that login to a the user database instead of master.
January 22, 2013 at 9:17 am
Thanks all, those are good ideas
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply