Post reply

drop a login no longer works here

  • June 13, 2011 at 6:02 pm

    #239903

    We have a dba who no longer works here.

    Now I would like to drop her login on a SQL server instance.

    There is no job created by her account.

    The only thing is there is a couple of database created by her initinally.

    Is that Ok that I just drop her account?

    Is this common practice to do like this?

    Thanks

  • June 13, 2011 at 7:39 pm

    #1338137

    As long as the login isn't mapped to users that own objects or databases, sure you can drop it. But I would check the ownership very carefully before you drop it.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • June 13, 2011 at 8:59 pm

    #1338144

    Thanks, I said in my post she created two databases, so she is the owner of the databases, correct?

    I just checked, if I right click the database -property, I can see the owner is her login.

    So maybe I'd better leave her account in security and not drop?

    Thanks

  • June 14, 2011 at 2:59 am

    #1338223

    You can try changing the db owner , else if your too worried you might do damage , try disabling the login.

  • June 14, 2011 at 4:25 am

    #1338252

    Look up sp_changedbowner in the Books Online. That will let you change the database owner to another login and then you can drop hers. I would recommend dropping her login on all servers. It's the right thing to do when someone leaves the company.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • June 14, 2011 at 9:24 am

    #1338468

    So shall I change the dbowner to sa using sp_changeowner, then drop the login?

    Thanks

  • June 14, 2011 at 9:41 am

    #1338480

    Yep, that would do it.

    You may also have to drop individual database users as well, especially if that login created objects out on the databases with itself as owner.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply