October 7, 2009 at 6:05 am
Hello Srs.
The DBA from the company where I worked has been dismissed and from now on, I'm the new one. The AD login of him, was already disabled and he can't access neither the network nor the sql servers anymore.
I have a question despite it: If I delete the old DBA login in the SQL SERVER, (he isadded to the sysadmin role), the databases and objects that he was owner, will be affected or maybe stop to work?
thank you so much...
Edvaldo Castro
October 7, 2009 at 7:20 am
edvaldocastro (10/7/2009)
Hello Srs.The DBA from the company where I worked has been dismissed and from now on, I'm the new one. The AD login of him, was already disabled and he can't access neither the network nor the sql servers anymore.
I have a question despite it: If I delete the old DBA login in the SQL SERVER, (he isadded to the sysadmin role), the databases and objects that he was owner, will be affected or maybe stop to work?
thank you so much...
Edvaldo Castro
it would be best practise to change the ownership of anything that he owned. Personally I would disable the account for the time being in sql server and remove it once you have dealt with any ownership issues,
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
October 7, 2009 at 2:44 pm
Normally I don't like to post "I agree posts", but in this case I will. I agree with Silverfox. Clean up ownership issues and then delete the login.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 7, 2009 at 2:59 pm
Ownership of database objects should not belong to individuals IMHO. Doing that causes issues like this one.
October 7, 2009 at 6:37 pm
Totall agree with Lynn here. You'll want to make sure the objects don't belong to an actual person. Probably need to institute that as a standard in your environment. That will ensure this isn't a problem in the future.
K. Brian Kelley
@kbriankelley
October 7, 2009 at 8:08 pm
K. Brian Kelley (10/7/2009)
Totall agree with Lynn here. You'll want to make sure the objects don't belong to an actual person. Probably need to institute that as a standard in your environment. That will ensure this isn't a problem in the future.
Do you mean for example, to create and set all owners of objetcs for the user "sqlservice" or "sql server agent" ? I also agree with your point...
October 7, 2009 at 8:23 pm
Or to use SQL Server based logins for that purpose that don't correspond to any real person.
K. Brian Kelley
@kbriankelley
October 7, 2009 at 8:30 pm
I understand an agree perfectlly with your point...
But... now.. the problem is installed, I have to correct it... and I think, I should not do it looking for jobs and objects manually in each server installed the SQL SERVER...
So.. thank you all of you...
Your answers had helped me a lot...
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply