non SA owned databases

Are there any issues with databases not being  owned by SA? I have just seen a healthcheck script which flags it as an issue if the database isnt owned by the default SA account? Why so, what are the risks?

For clarity, is there an easy way to identify which account owns which database via SQL?
LVL 3
pma111Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Tony GiangrecoConnect With a Mentor Commented:
Your backup app may have a problem with it. Have you address that?
0
 
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
if you deleted the login which is the owner of the database, you would then have to perform a db owner change.

backup software shall use "some" account with sys_adm powers, which is the equivalent in regards to "power" as sa account.
0
 
pma111Author Commented:
So in all if the db owner account has sa permissions and is never disabled/removed in AD, there is no issue?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Scott PletcherConnect With a Mentor Senior DBACommented:
>> For clarity, is there an easy way to identify which account owns which database via SQL? <<

Yes: the sys.databases view provides the owner_sid for every db.  You can use that value to join to sys.database_principals to get the name of the login.


SELECT d.name, sp.name AS owner_name
FROM sys.databases d
LEFT OUTER JOIN sys.server_principals sp ON
    sp.sid = d.owner_sid
0
 
pma111Author Commented:
So in all if the db owner account has sa permissions and is never disabled/removed in AD, there is no issue?
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
exactly
0
All Courses

From novice to tech pro — start learning today.