how to drop erroneous user from db in 2005

Hi All
i have a row in sysusers table with name 'analyst'. The same login exist in
master..syslogins table but sid's are different. It likely happened when
somebody loaded db but I really don't know.
In 2000 I would remove this row from sysusers table. In 2005 I can't do
that. Which essentially leaves me with option not to use 'analyst' login at
all becase it works in some db's and not others.
What should I do in this situation? How can I remove this erroneous row
which does not have matching sid in master..syslogins table?
Hi
Have you checked that the user is not orphaned with EXEC
sp_change_users_login 'report' ?
In SQL 2005 it is possible to CREATE USER <user> WITHOUT LOGIN and you can
use ALTER USER <user> WITH LOGIN = 'loginname' to remap the sids.
John
John
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:F32E5B19-0559-4953-9069-BA209533E549@.microsoft.com...
> Hi All
> i have a row in sysusers table with name 'analyst'. The same login exist
> in
> master..syslogins table but sid's are different. It likely happened when
> somebody loaded db but I really don't know.
> In 2000 I would remove this row from sysusers table. In 2005 I can't do
> that. Which essentially leaves me with option not to use 'analyst' login
> at
> all becase it works in some db's and not others.
> What should I do in this situation? How can I remove this erroneous row
> which does not have matching sid in master..syslogins table?
|||Hi John
It is orphaned user. I just did not know how to handle it other than remove
it in '2000' fashion. I will try your way tomorrow.
Thank you, Gene.
"John Bell" wrote:

> Hi
> Have you checked that the user is not orphaned with EXEC
> sp_change_users_login 'report' ?
> In SQL 2005 it is possible to CREATE USER <user> WITHOUT LOGIN and you can
> use ALTER USER <user> WITH LOGIN = 'loginname' to remap the sids.
> John
> John
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:F32E5B19-0559-4953-9069-BA209533E549@.microsoft.com...
>
>
|||Hi Gene
You should be able use the same methods in 2005 as you used in SQL 2000 see
http://support.microsoft.com/kb/274188/
John
"Gene." wrote:
[vbcol=seagreen]
> Hi John
> It is orphaned user. I just did not know how to handle it other than remove
> it in '2000' fashion. I will try your way tomorrow.
> Thank you, Gene.
> "John Bell" wrote:

how to drop erroneous user from db in 2005

Hi All
i have a row in sysusers table with name 'analyst'. The same login exist in
master..syslogins table but sid's are different. It likely happened when
somebody loaded db but I really don't know.
In 2000 I would remove this row from sysusers table. In 2005 I can't do
that. Which essentially leaves me with option not to use 'analyst' login at
all becase it works in some db's and not others.
What should I do in this situation? How can I remove this erroneous row
which does not have matching sid in master..syslogins table?Hi
Have you checked that the user is not orphaned with EXEC
sp_change_users_login 'report' ?
In SQL 2005 it is possible to CREATE USER <user> WITHOUT LOGIN and you can
use ALTER USER <user> WITH LOGIN = 'loginname' to remap the sids.
John
John
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:F32E5B19-0559-4953-9069-BA209533E549@.microsoft.com...
> Hi All
> i have a row in sysusers table with name 'analyst'. The same login exist
> in
> master..syslogins table but sid's are different. It likely happened when
> somebody loaded db but I really don't know.
> In 2000 I would remove this row from sysusers table. In 2005 I can't do
> that. Which essentially leaves me with option not to use 'analyst' login
> at
> all becase it works in some db's and not others.
> What should I do in this situation? How can I remove this erroneous row
> which does not have matching sid in master..syslogins table?|||Hi John
It is orphaned user. I just did not know how to handle it other than remove
it in '2000' fashion. I will try your way tomorrow.
Thank you, Gene.
"John Bell" wrote:
> Hi
> Have you checked that the user is not orphaned with EXEC
> sp_change_users_login 'report' ?
> In SQL 2005 it is possible to CREATE USER <user> WITHOUT LOGIN and you can
> use ALTER USER <user> WITH LOGIN = 'loginname' to remap the sids.
> John
> John
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:F32E5B19-0559-4953-9069-BA209533E549@.microsoft.com...
> > Hi All
> > i have a row in sysusers table with name 'analyst'. The same login exist
> > in
> > master..syslogins table but sid's are different. It likely happened when
> > somebody loaded db but I really don't know.
> > In 2000 I would remove this row from sysusers table. In 2005 I can't do
> > that. Which essentially leaves me with option not to use 'analyst' login
> > at
> > all becase it works in some db's and not others.
> > What should I do in this situation? How can I remove this erroneous row
> > which does not have matching sid in master..syslogins table?
>
>|||Hi Gene
You should be able use the same methods in 2005 as you used in SQL 2000 see
http://support.microsoft.com/kb/274188/
John
"Gene." wrote:
> Hi John
> It is orphaned user. I just did not know how to handle it other than remove
> it in '2000' fashion. I will try your way tomorrow.
> Thank you, Gene.
> "John Bell" wrote:
> > Hi
> >
> > Have you checked that the user is not orphaned with EXEC
> > sp_change_users_login 'report' ?
> >
> > In SQL 2005 it is possible to CREATE USER <user> WITHOUT LOGIN and you can
> > use ALTER USER <user> WITH LOGIN = 'loginname' to remap the sids.
> >
> > John
> >
> > John
> >
> >
> > "Gene." <Gene@.discussions.microsoft.com> wrote in message
> > news:F32E5B19-0559-4953-9069-BA209533E549@.microsoft.com...
> > > Hi All
> > > i have a row in sysusers table with name 'analyst'. The same login exist
> > > in
> > > master..syslogins table but sid's are different. It likely happened when
> > > somebody loaded db but I really don't know.
> > > In 2000 I would remove this row from sysusers table. In 2005 I can't do
> > > that. Which essentially leaves me with option not to use 'analyst' login
> > > at
> > > all becase it works in some db's and not others.
> > > What should I do in this situation? How can I remove this erroneous row
> > > which does not have matching sid in master..syslogins table?
> >
> >
> >