Have Geek Brain

Keeping a SQL Server Dev Environment Up to Date

I am trying to figure out how best to keep development servers in sync with production servers. I originally intended to restore backups from the production environment to the development environment every week or so, however, I realized that this would wipe out any actual development that was done during the week.

I feel like this is a fairly common hurdle, so I hope someone out there can shed some light on how they solve the problem. I looked online briefly but didn't see anything, so any suggestions would be greatly appreciated.

Thanks!

+2


a source to share


2 answers


Red Gate has several products you can look at:



They allow schema and data to be compared and synchronized respectively between two databases.

+1


a source


Any changes made to the development environment must be pushed to production at some point. Therefore, every change made in the dev environment must exist as a patch (sql script). To keep the developer in sync with production, you simply restore the production backup and apply any newly developed fixes.



+1


a source






More articles:


All Articles