Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
martin553
Starting Member
2 Posts |
 Posted - 2007-03-16 : 06:39:52
|
| Hi all,When I create datbases in Enterprise Manager the user dbo isn't mapped to the login name sa, which it should be by default. I know I easily can fix the problem with sp_changedbowner. But what I wonder is why isn't dbo mapped to sa in the first place and how do I reastablish the default mapping between the two?Thanks in advanceMartin |
|
|
rlaubert
Yak Posting Veteran
96 Posts |
Posted - 2007-03-16 : 07:52:39
|
| Just want to make sure, you are checking under Security for the SA assignment and not in the database. Database will only show the DBO role and no assignment for SA. Under the server security settings SA should show database owner for each database.I couldn't find any settings that changes these defaults. But will keep looking, have a couple of servers where I would like to limit the dbo membership, although the SA could always take ownership if needed.Raymond LaubertMCDBA, MCITP:Administration, MCT |
 |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-03-16 : 14:29:17
|
| By default, a database is owned by the login that creates the database. In the distant past, this had to be sa. Now it can by anyone who is a member of the local administrators group. There is no harm to leaving the non-sa user as the owner of the database. Unless you have cross-database-ownership-chaining set to on. Or if you need to lock that particular user out of the server. |
|
|
|
martin553
Starting Member
2 Posts |
Posted - 2007-03-16 : 18:48:51
|
quote:
Originally posted by mcrowley
By default, a database is owned by the login that creates the database. In the distant past, this had to be sa. Now it can by anyone who is a member of the local administrators group. There is no harm to leaving the non-sa user as the owner of the database. Unless you have cross-database-ownership-chaining set to on. Or if you need to lock that particular user out of the server.
The problem isn't that sa doesn't own the database, the problem is that noone owns the database. In the login column for user dbo in the User entry of the database in EA there is nothing. How do I reconfigure SQL Server so sa shows up there when I create another database? |
|
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-03-19 : 10:51:18
|
| Only create databases as sa. |
|
|
|
|
|
|
|
|
dbo not sa in new db, is there a permanent fix