If you get this message : Error 15023: User already exists in current
database
then try following:
delete the user from database-folder--> user-tab and also delete user
for security-folder--> logins
and then create same user againYou can use sp_change_users_login to fix that. Here are some links that may
help:
http://www.databasejournal.com/feat...cle.php/2228611
Transferring Logins
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
Andrew J. Kelly
SQL Server MVP
"Sonal Chauhan" <sj2909@.yahoo.com> wrote in message
news:1e44a73a.0406071204.6d79cfb7@.posting.google.com...
> If you get this message : Error 15023: User already exists in current
> database
> then try following:
> delete the user from database-folder--> user-tab and also delete user
> for security-folder--> logins
> and then create same user again
Thursday, March 22, 2012
Error 15023: User already exists in current database
Labels:
current,
currentdatabasethen,
database,
database-folder-gt,
error,
exists,
followingdelete,
message,
microsoft,
mysql,
oracle,
server,
sql,
user,
user-tab
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment