stored procedure and packages ownership on MS SQL 2000

  • SQLGuy64

    Ten Centuries

    Points: 1051


    I'm writing about stored procedure and packages ownership on MS SQL 2000.  A developer is leaving our group and he has created stored procedures and packages under his windows 2003 logon.  His logon is assigned to the system administrator role.  Will I have any problems when his windows logon is retired?

    thank you

  • dm

    Ten Centuries

    Points: 1105

    You might have problems, so its best to change the ownership of the objects.  For the stored procedures, if they are owned by the developers login and not 'dbo', use the system stored procedure sp_changeobjectowner to change the ownership.  For the packages, make sure they are not password protected and use this article to change the package owner:

    Hope this helps,



  • Chris Hedgate

    One Orange Chip

    Points: 25041

    The procedures cannot be owned by his login. Procedures are owned by users. His login might however be mapped to a specific user which owns the procedures. That user might be orphaned if his login is removed. However, you said that his login "is assigned to the system administrator role". I interpret that as if his login account is a member of the sysadmin fixed server role. If so then any object he creates, in any database, will be owned by dbo. That is of course unless he specifically created them with another user specified as owner.

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

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