This is a multi-part message in MIME format.
--=_NextPart_000_0015_01C3DBB8.722998E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sorry but i think i was not clear enough..
I have a SQL Server 7.0 Desktop installed in my computer. When i = restore a back up
from a SQL SERVER 7.0 Standart it, restore all tables from the database = but not logins.
When I create the logins in the Standart Edition, I created it one for = each user and sing it
by database default my database.
this users appear in the tree view, in the Database User folder. When i restore the database all there are not users, asingned in the = database...
only, Roles and, in this ones, a Public one, that contain all users that = i created.
I can't delete this users, and i can't create a new one with the same = name, because an Error
come's up..
Error 15023: User or role 'REMI'alredy esists in the current database
now i don't know what to do..
any help it will be apreciated..
Remi
--=_NextPart_000_0015_01C3DBB8.722998E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Sorry but i think i was not clear enough..
I have a SQL Server 7.0 Desktop = installed in my computer. When i restore a back up
from a SQL SERVER 7.0 Standart it, = restore all tables from the database but not logins.
When I create the logins in the = Standart Edition, I created it one for each user and sing it
by database default my = database.
this users appear in the tree view, in = the Database User folder.
When i restore the database all there = are not users, asingned in the database...
only, Roles and, in this ones, a Public = one, that contain all users that i created.
I can't delete this users, and i can't = create a new one with the same name, because an Error
come's up..
Error 15023: User or role 'REMI'alredy = esists in the current database
now i don't know what to = do..
any help it will be = apreciated..
Remi
--=_NextPart_000_0015_01C3DBB8.722998E0--I am not sure if I understand everything, but let me try. Logins are in
master database, so it is normal they are not restored with a user database.
You can script them on the source and implement the script on the
destination server. I guess we are talking about SQL logins. You cn map them
to db users with sp_change_users_login system SP - check it in Books OnLine.
HTH,
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.|||Thank you that resolve the problem...
Remi
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> escribió
en el mensaje news:e3MIR0$2DHA.3196@.TK2MSFTNGP11.phx.gbl...
> I am not sure if I understand everything, but let me try. Logins are in
> master database, so it is normal they are not restored with a user
database.
> You can script them on the source and implement the script on the
> destination server. I guess we are talking about SQL logins. You cn map
them
> to db users with sp_change_users_login system SP - check it in Books
OnLine.
> HTH,
> --
> Dejan Sarka, SQL Server MVP
> Please reply only to the newsgroups.
>
Friday, March 9, 2012
Login and User Problems
Labels:
_nextpart_000_0015_01c3dbb8,
charset,
content-type,
database,
format,
iso-8859-1,
login,
message,
microsoft,
mime,
multi-part,
mysql,
oracle,
plain,
server,
sql,
text,
user
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment