February 25, 2009 at 2:50 pm
How does everyone keep their DR and PROD in sync. I'm not talking about log shipping and mirroring. I mean after your choice of replicating data is setup... How do you go about keeping logins, jobs, linked servers, backup devices, DTS packages, SSIS packages and all the other stuff in sync?
We have a mixture of SSIS packages and sql scripts that take care of alot of things (logins, linked servers, dts, SSIS) but we are still lacking in some areas. I wanted to see what everyone else was using to attack this problem.
thanks for the input.
February 25, 2009 at 4:20 pm
For logins transfer, you have script in Microsoft KB's..For jobs you can do it through SSIS..SSIS packages, i think in same way, except you have to change parameters (if you have) and place package files on other server...
If you are not talking about Mirroring and Log shipping, then the server is not called DR..replication allows you, but not preferred for DR (in my view)..
--Sudhie
February 25, 2009 at 9:06 pm
Hello,
It is a good idea to (always) use Scripts to deploy to your Prod environment, that way you can also apply them to your DR Site, and keep things in Synch. The other big advantage is you can test the deployment package works on a “staging” server, before going live.
Additionally we use RedGate’s SQL Compare tools to do a lot of our inter Environment Synchronisation work. It includes a handy wizard to build update scripts too. (There are similar tools from other vendors e.g xSQL).
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply