Projects tagged ‘compare’ and ‘database’

This is a command line tool written in Python. It displays all the differences between two database schemas. The schema are provided as SQL dump. 1. ExampleInputdb1.sql: sql dump of a database with ... [More] a single table: 'person' CREATE TABLE `person` ( `last name` varchar(50) NOT NULL, `date_of_birth` varchar(45) NOT NULL, PRIMARY KEY (`last name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;db2.sql: sql dump of the same database after adding a new table 'car' and modified fields in the 'person' table. CREATE TABLE `car` ( `color` varchar(50) NOT NULL, `number_plate` varchar(50) NOT NULL, `brand` varchar(50) NOT NULL, PRIMARY KEY (`number_plate`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `person` ( `last name` varchar(50) NOT NULL, `date_of_birth` datetime NOT NULL, `first_name` varchar(45) NOT NULL, PRIMARY KEY (`last name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;Commandpython compdb.py db1.sql db2.sqlOutput% FIELD: person.date_of_birth `date_of_birth` varchar(45) NOT NULL => `date_of_birth` datetime NOT NULL + FIELD: person.`first_name` varchar(45) NOT NULL + TABLE: car 3 difference(s).2. Notation%: difference +: new field or table -: missing field or table 3. LimitationsCurrently works only with MySQL dumps Obviously this tool cannot detect when the name of a field or a table has changed! 4. MotivationThis script was originally written to help me keep track of the evolution of Django models (hence the Python implementation). Before upgrading a staging server, I would compare the SQL dump from my development database (generated with mysqldump -d or with python manage.py sql) with the dump from my staging server. Note that more sophisticated tools have been developed for this purpose, search for 'django schema evolution' on any search engine to find them. This tool was developed as part of a UML to Django conversion project. 5. FeedbackYour comments and contributions are welcome. [Less]

As a software product evolves it is inevitable that the underlying database schema changes and you have to make sure any changes you make in the development cycle are made to all other database as the ... [More] software is distributed. In all our products we include a database management module that propagates changes out to live databases and ensures the version of the software matches the database schema. In the early stages of development though the schema changes made by designers and developers come fast and furious and it can be difficult keeping track of them and propagating them to other databases. At Paritor we have this problem and find it can be a long winded job comparing databases manually. There are tools out in the marketplace to analyse databases, show differences and even script any necessary changes but apart from the fact that they all cost money they all seem to be a "Sledge Hammer to Crack a Walnut". I therefore sat down the other morning and put together a simple utility to open up two database, analyse the differences and report on what it finds. I wrote it as a WPF application, mainly because I wanted to use the WPF Document namespace to create the report and show it using the WPF Document Viewer. You could easily write it as a Windows forms and use System.Drawing.Print or even produce a Crystal Report. [Less]

Open DbDiff is a very simple tool to synchronize two versions of database.

Open DBDiff is an open source database schema comparison tool for SQL Server 2005/2008. It reports differences between two database schemas and provides a synchronization script to upgrade a database from one to the other.