SQL 7.0 using SQL/Windows authenication.
A DB backup was restored from one server to another which
had a new install of SQL 7.0.
Problem:
In EM/Security, if I try to add the user login 'xxx' with
access to the restored DB, SQL says the login name
already exists in the the DB. Yet, it doesn't exist, that
I can see any where. If I try to access the DB from an
ODBC connection using the login 'xxx' it denies access.
I tried droplogin 'xxx', but that didn't help.
Any ideas?
Thanks,
DonRead up on sp_change_users_login within Books Online. I am sure that it =
will solve your problem.
--=20
Keith
"Don" <anonymous@.discussions.microsoft.com> wrote in message =
news:763a01c406aa$374e45a0$a601280a@.phx.gbl...
> SQL 7.0 using SQL/Windows authenication.
>=20
> A DB backup was restored from one server to another which=20
> had a new install of SQL 7.0.=20
>=20
> Problem:
> In EM/Security, if I try to add the user login 'xxx' with=20
> access to the restored DB, SQL says the login name=20
> already exists in the the DB. Yet, it doesn't exist, that=20
> I can see any where. If I try to access the DB from an=20
> ODBC connection using the login 'xxx' it denies access.
> I tried droplogin 'xxx', but that didn't help.
> Any ideas?
> Thanks,
> Don
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment