Post reply

Any risks to changing owner?

  • December 17, 2008 at 8:13 am

    #73163

    I'm new to this DBA hat I'm currently wearing, so pardon my tentiveness here.

    Here's the situation. I inherieted a SQL2005 server that seems to be in sort of rocky shape. When the last DBA left, someone removed his login from the server. Unfortunately, he was the owner of several databases.

    Now these databases are orphaned and ownerless. It doesn't seem to be causing any major problems, but it does goof up some of SSMS's functionality. And as a new DBA, I still need my GUI! 🙂

    Anyhow, from what I've read it's recommended SA own everything anyway. I'm getting ready to change the owner of these DBs to SA, but I was wondering if there are any risks? What kinds of things could it screw up? I'd read a message somewhere that said something about it changed permissions on underlying objects, which sounds like a big deal. But I'd not seen that mentioned anywhere else, so I'm a bit confused.

  • December 17, 2008 at 9:28 am

    #913958

    Changing the database owner doesn't change permissions on objects, but it does change the ownership of any objects already owned by DBO. IMO, it's a good thing to have SA be the owner of all the databases because, unlike a real person's login, it's not likely to be dropped.

    Greg

  • December 17, 2008 at 4:45 pm

    #914247

    We assign all such ownership as "dbo"... prevents such hassles in the future.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 3 (of 3 total)

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