October 1, 2012 at 7:04 am
We have a unneeded 2008 enterprise database (no enterprise features needed). We're attempting to migrate back to standard 2008. That effort is unsupported by Microsoft. While we use replication, we do not use any enterprise features.
When the database was restored in the standard environment, everything looked ok. when a login was created and we attempted to map it ("user mapping") to the new database we got an error message "15023 - user, group or role in 'xxx' already exists" in the current database.
I ran "EXEC sp_change_users_login 'Report'" and that showed the user does exist in the
database that was copied over. My question is how to get them back in sync.
My inclination is to run "EXEC sp_change_users_login 'update_one', 'xxx', 'xxx'"
My question - is the correct route to go? Any comments would be appreciated - thank you.
October 1, 2012 at 7:53 am
Yes that will resolve the issue, also look at ALTER USER as if I remember correctly sp_change_users_login is scheduled for removal in a future version of SQL.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply