August 11, 2003 at 1:40 pm
When you first create a database using EM, the dbo user for that database is not mapped to a login account. After changing the dbo to an existing user, I would like to change it back to the original setting, or map it to an admin user like sa.
However, I don't think I can pass a null or blank value to the sp_changedbowner proc. I have tried both and received an error each time that '' or (null) is not a valid login.
That being said, I have three questions.
1. What is the best policy for setting dbo on each database? Should it be a login associated with that db, or an admin login like sa?
2. Is it possible to return the dbo user to its original, un-mapped state?
3. What are the security implications of having dbo exist as an un-mapped user?
I have read Steve Jones article "Who Owns That Database?" as well as Brian Kelley's "SQL Server 2000 SP 3: What's New in Security" but neither applied to this particular issue... (At least as far as I could tell 🙂 )
Thanks!
Dan B
August 14, 2003 at 8:00 am
This was removed by the editor as SPAM
August 14, 2003 at 11:18 am
I typically set all mine to sa - based on the way I manage/allow access, it doesn't really make a difference.
Andy
August 14, 2003 at 11:30 am
Thanks Andy! I will give this a try...
Dan B
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply