Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JCAlexandres
Starting Member
5 Posts |
 Posted - 2008-04-30 : 10:29:14
|
| Hi;I have the situation of creating a disaster/recover (DR) database on a second SQL 2000 server, but when we try to run the application we get an error because aparently the user that installed the application is hard-coded and bound to the SQL sid for that user, which eventually involves two schemas.I have done a work-around process on the DR server changing the ownership of objects for the user with the issue, dropping the user, creating the user, and putting the objects back, this works but the downfall, is time consuming since this user owns 80% of the objects in the database, and of course there are over 1000 tables among other objects like views and stored procedures.So I am thinking if there is a way to synchronize the user at the SQL servers level rather than at the application, this will allow to restore a database from production to DR and use it right away without the need of tweaking the user.Let me know your thoughts on this.Thank you!J.C. AlexandresIT Professional |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-30 : 21:34:41
|
| Microsoft has copy sql login script, you can find it in TechNet. |
 |
|
|
|
|
|
Synchronizing a user SID on two SQL Servers