Post reply

sysuser table

  • February 18, 2004 at 12:38 pm

    #82318

    Any one knows what status 16 means in sysusers table? I was cleaning orphan users and found user named: \test. I cannot see this user in sp_helpuser result. It is orphan user, and has status 16 in sysusers table. I cannot drop it. It is not db role.

     

  • February 18, 2004 at 2:43 pm

    #494593

    I'm not sure what the 16 means- that column is marked as for internal use only.  Did you try to drop the user using the sp_dropuser command?  That table could be edited but unless you verify that all linked tables do not refer to this row, I recommend not editing sysusers.

    Francis

  • February 19, 2004 at 7:39 am

    #494701

    Status 16 means this is record for an alias. 

    '\test' is not username, it means this alias for login 'test'.

    This login is aliased to the userid, specified in altuid column.

    To drop it use sp_dropalias 'test'.

  • February 19, 2004 at 8:25 am

    #494713

    This is correct, also in sysusers table there is a column 'isaliased' and for \test has value 1.

    Thanks a lot.

  • February 19, 2004 at 10:38 pm

    #494855

    Agreed , the possible cause of these may be from conversion of a V6.5 sql server environment to V7. The conversion process retains the users aliased to dbo under the old 6.5 method and needs a way to store them in 7. It does this using this value, I also remember that V7 EM won't display these users as aliased, the users special status as aliased to dbo is hidden.

  • July 20, 2004 at 9:36 am

    #515295

    Does any one have a list of what the Status are and there meaning?

  • July 20, 2004 at 10:02 am

    #515302

    What does status 12 mean?

  • July 20, 2004 at 12:36 pm

    #515328

    What is the definition of an orphaned user?

  • July 20, 2004 at 7:41 pm

    #515380

    I suppose there may be different definitions but the one I would use is as follows:

    An orphaned user is a user that is defined in a database,  that is an entry exists in a databases sysuser table for which no link exists back to the master databases syslogins table.  The link between 'user' and 'login' has been broken.  This can occur when copying a database from one server to another for example. One solution for this is to use the sp_change_users_login proc to fix the link between a user and a login.  

  • July 21, 2004 at 10:17 am

    #515492

    Thank you for the definition!

  • January 18, 2007 at 1:32 pm

    #684100

    A status list would sure help!!!

    I´m having trouble with some queries made to run under SQL 2000 that are now running under SQL 2005.

    In SQL 2005 SYSUSER table has been subtituted by sys.database_principal which does not contain the status column.

    Does anyone knows what happened.

    Thanks.

Viewing 11 posts - 1 through 10 (of 10 total)

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