Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have two SQL 2005 instances that reside on different networks. I need to backup a database from instance A and restore it to a database in instance B on a weekly basis so that both databases hold the same data. After the restore, logins SIDS on database B are changed and therefore users can’t log into database B and connection strings for the web application it supports are broken. Is there a work around for this? Thanks.
There is a stored procedure for that:
sp_change_users_login(see: http://msdn.microsoft.com/en-gb/library/ms174378.aspx). In particular, take a look at theAuto_Fixaction. However, be aware that this SP is going to be deprecated in the future.Insead, we’re now supposed to use
ALTER USER(see: http://msdn.microsoft.com/en-gb/library/ms176060.aspx).