How to synchronize development and production database.

Question

Do you know any applications to synchronize two databases - during development sometimes it's required to add one or two table rows or new table or column. Usually I write every sql statement in some file and during uploading path I evecute those lines on my production database (earlier backing it up). I work with mySQL and postreSQL databases.

What is your practise and what applications helps you in that.

Answer 1

Have scripts (under source control of course) that you only ever add to the bottom off. That combined with regular restores from your production database to dev you should be golden. If you are strict about it, this works very well.

Otherwise I know lots of people use redgate stuff for SQLServer.

Answer 2

Siebel (CRM, Sales, etc. management product) has a built-in tool to align the production database with the development one (dev2prod).

Otherwise, you've got to stick with manually executed scripts.

Answer 3

Navicat has a structure synchronisation wizard that handles this.

Answer 4

For PostgreSQL you could use Another PostgreSQL Diff Tool . It can diff two SQL Dumps very fast (a few seconds on a db with about 300 tables, 50 views and 500 stored procedures). So you can find your changes easily and get a sql diff which you can execute.

From the APGDiff Page:

Another PostgreSQL Diff Tool is simple PostgreSQL diff tool that is useful for schema upgrades. The tool compares two schema dump files and creates output file that is (after some hand-made modifications) suitable for upgrade of old schema.

Answer 5

Another vote for RedGate SQL Compare

http://www.red-gate.com/products/SQL_Compare/index.htm

Wouldn't want to live without it!

Edit: Sorry, it seems this is only for SQL Server. Still - if any SQL Server users have the same question I'd definitely recommend this tool.

Answer 6

I solve this by using Hibernate. It can detect and autocreate missing tables, columns, etc.

Answer 7

I really like the EMS tools.

There tools are available for all popular DB's and you have the same user experience for every type of DB.

One of the tools is the DB Comparer.

Answer 8

If you write your SQL statements for your development database (which are, I imagine, series of DDL instructions such as CREATE, ALTER and DROP), why don't you keep track of them by recording them in a table, with a "version" index? You will then be able to:

1. track your version changes
2. make a small routine allowing the "automatic" update of your production database by sending the recorded instructions to the database.

Answer 9

You might want to check out any of MySQL related DBSync tools from the link in my profile. Read more about the syncronization process here

Answer 10

You asked for a tool or application answer, but what you really need is a a process answer. The underlying theme here is that you should be versioning your database DDL (and DML, when needed) and providing change scripts to be able to update any version of your database to a higher version.

This set of links provided by Jeff Atwood and written by K. Scott Allen explain in detail what this ought to look like - and they do it better than I can possibly write up here: http://www.codinghorror.com/blog/2008/02/get-your-database-under-version-control.html

Answer 11

TOAD

saved many an ass several times in the past. Why do people run sql with no exit strategy?

the redgate one is good also.

Answer 12

You could add some automation to your current way of doing things by using dbDeploy or a similar script. This will allow you to keep track of your schema changes and to upgrade/rollback your schema as you see fit.