Hello:
In another posting, I had mentioned the age-old practice requiring the change of GP user passwords when moving GP data from one SQL server to another.
I'm having a hard time convincing DBAs that I work with that this has to be done, despite the fact that I have proven on at least two occasions that this practice does indeed have to be conducted, unless you use a DNS Alias.
Now, I spoke with one of our senior DBAs who says that there is a plan to "replicate" GP's SQL data from one server to another rather than "transferring" the data. He feels that, by using replication instead, the end users' GP passwords will remain the same in the new replicated environment.
The reasoning behind such replication has to do with disaster recovery. If the live GP environment goes down, the replicated environment would be used immediately by end users. With the replicated environment, this senior DBA says that GP users can continue with their daily work as usual without having to have new GP passwords.
Is this correct? Again, in all of the documentation that I have used over the years and in all of the times that I have moved GP SQL data, users' GP passwords had to be changed. (I have never worked with DNS Aliases.)
Thanks!
John
