January 21, 2016 at 9:38 am
We have multiple databases which when viewing the properties in Management Studio, indicates the owner is an administrative account (not a USER account or 'SA') with sysadmin privileges. That is what you should have configured.
The concern, we couldn't help but notice 'SA' is mapped to several user databases. 'SA' is not part of the ODBC connection. So it's mapped but really appears to have no role. Do you remove it? Is it worth our while to be concerned about it or ignore it? And if it is a concern, how do you remove it?
Any comments would be appreciated. Thanks.
January 21, 2016 at 10:56 am
Personally I prefer making the database owner 'sa'. It can't cause an inadvertent privilege increase, since sa is sysadmin always, it can't cause problems as will happen if a domain account owns a DB and the domain account is removed from AD, and it means that when dropping a login you don't have to worry about whether it owns any databases.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 28, 2016 at 11:00 pm
the best way as Gail suggested is to make owner as 'sa'
Another way is(if you want a db owner as a windows a/c) then make SQL server service a/c as a dbowner.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply