Background:
We are launching a web application in which each user has a login on the system. The application login is mapped to the actual SQL Server 2005 input (which we need to create). Our disaster recovery and recovery sites are just copies of this installation. A production database is created on a nightly basis, the dump is archived, and we restore dev and DR using this file. When this is done, we need to run sp_change_users_login for each user in order to reassign the database user to the SQL login.
Problem:
When a user changes his password during production, the password for SQL login changes. It does not sync with dev / DR, so if they try to log into one of these sites, they cannot and must reset their password. Is there a [good] way for these SQL logics to synchronize with multiple installations?
The next version of this product eliminates the need for SQL login, but updating is not the current priority.
source
share