Post reply

DID NOT have to re-establish the login and db user link after restoring database

  • June 30, 2014 at 9:38 am

    #296118

    We have SQL Server 2012 running on Windows 2008 Server. We copied databases from one server to another server using the backup/restore method. Once the databases were restored on the destination server, the users had their permissions they previously had on the source server. (On the destination server, the server logins were created before the restore was performed.) I DID NOT have to re-establish the login and db user link using the sp_change_users_login stored procedure.

    I thought I would have had to re-establish the login and db user link. Is this automatically done with SQL Server 2012?

    Thanks in advance, Kevin

  • June 30, 2014 at 9:46 am

    #1725920

    stating the obvious, windows users would not need to be resynced as orphans.

    if we are talking about SQL users, i can certainly think of a classic scenario where this would be true:

    someone used sp_help_revlogin to script out the users with their hashed passwords, and ran the script on the other server.

    in that situation, the sids would match, and no orphans would need fixing when you restored the database.

    could that be what has happened here?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply