June 6, 2005 at 3:44 am
Hi,
In our company we are working with three separate environments: test, acceptance and production. Sometimes I have to make sure that these three databases (per application) are exactly the same again. So I copy the productiondatabase over the databases for test and acceptance. The problem here is the difference in accounts for databaseusers / sqlserver logins.
The configuration is like this: per environment are the domainaccounts named like this: "DOMAIN\t_user", "DOMAIN\a_user" and "DOMAIN\user". They are mapped to databaseusers like: "t_user", "a_user" and "user". After copying a database to another environment these logins are broken of course and I have to delete the "wrong users" and to create new databaseusers mapped to the right SQL Serverlogins. I hope that I make some sense here...
Does anybody have some experience with this concept? I wonder how you handle this. Is it better to have neutral databaseusers for instance? I would like to hear your opinion about this.
Thanks,
Peter.
June 6, 2005 at 5:20 am
We have this problem as well. What we have done is created a script that removes all users (except for sa) and re-adds the correct ones. of course this still needs a quick manual scan to ensure correctness.
Overall it works very well for us.
Good Hunting!
AJ Ahrens
webmaster@kritter.net
June 9, 2005 at 1:50 am
Hello AJ Ahrens,
Do you use neutral accounts or accounts like a_account, t_account? I tried both ways but it's both difficult. Another problem is that some accounts own objects, so I can not easily drop them. Anyway, can you send me your script for this user-correction? It sounds like it might be handy!
Thanks,
Peter.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply