Re: orphaned 'aliased' user

From: Russell Fields (RussellFields_at_NoMailPlease.Com)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 16:51:48 -0400

Peter,

>From your comments you certainly seem to know about the topic
Troubleshooting Orphaned Users (BOL)
http://tinyurl.com/7yjwt

It seems like you may be stuck with the ugly process of hacking the system
table to fix this. (Not too bad in this case, but to be avoided as a general
policy.) You should be able to allow updates to system tables, then delete
the troublesome row. Then be sure to disallow updates again.

allow updates Option (from the BOL)
http://tinyurl.com/4juy2

Russell Fields

"Peter Feakins" <PeterFeakins@discussions.microsoft.com> wrote in message
news:6962B92D-1ED2-4A69-8B30-7DC9D704C8DD@microsoft.com...
> We have a database that we detached and reattached on a new server. We've
> corrected all of the orphaned users except for one that appears to be an
> alias. The value for 'isaliased' in sysusers is 1 and the value for issql
is
> 0. We've transferred the login with which it was originally associated,
> however, the sid value has changed. It appears that we can't use
> sp_change_users_login since the user is not an sql user, and the
sp_addalias
> inserts a new sysusers record, rather than update the existing record.
Any
> suggestions?