Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Individual users as Owners


Individual users as Owners

Author
Message
dan-572483
dan-572483
SSChasing Mays
SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)SSChasing Mays (641 reputation)

Group: General Forum Members
Points: 641 Visits: 1958
As we know, when databases and SQL Agent jobs are created the owner is set by default to the user who created them. We've changed many of these to sa or an appropriate AD Service Account, but there are still several objects scattered among many instances where objects are owned by individules' Windows logins.

At this time we're facing a reorganization where the existing DBAs are being laid off and replaced by outsourced DBA support. How much of a problem is this (for the database processes that is)?

My underdanding of what "owner" means is that the owner can access these objects while bypassing normal secuity checks. If that is all, then will everything continue to work when the AD accounts are disabled? How about Agent Jobs? What other gotchas are when individual's accounts are disabled? (Not that it will be my problem when this happens, but while I'm still here I do feel responsible to prevent future issues).
Koen Verbeeck
Koen Verbeeck
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16447 Visits: 13202
If I recall it correctly, some SQL Server Agent jobs owned by the DBA at a previous project started giving issues when the DBA was fired and his account was removed.



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
Lempster
Lempster
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2683 Visits: 1657
Koen Verbeeck (6/10/2014)
If I recall it correctly, some SQL Server Agent jobs owned by the DBA at a previous project started giving issues when the DBA was fired and his account was removed.


Yes, you'll get a message in the SQL Agent log along the lines of: "unable to determine if domain\account has server access."

Regards
Lempster

EDIT: Added missing closing quote marks.
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47241 Visits: 44377
It can be a problem when the domain account is removed. For databases most things will work, then a few things (like replication) will give odd error messages. Jobs may or may not run depending what they need to access.


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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


LightVader
LightVader
SSC Eights!
SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)SSC Eights! (819 reputation)

Group: General Forum Members
Points: 819 Visits: 2892
We had one here a few years ago. There was a consultant that designed a database and application for us. A few months after he left, his AD account was removed and the jobs stopped working altogether (I don't remember the exact error message). Once we changed the job owner, everything worked again.

ETA: This was in SQL 2005.



The opinions expressed herein are strictly personal and do not necessarily reflect the views or policies of my employer.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search