SQL Delta Cross Platform or SQL DXP for short is a
cross platform database compare tool.
We have three versions in development and the three are:
- SQL DXP Premium supporting SQL Server, Oracle and MySQL.
- SQL DXP SM supporting SQL Server and MySQL.
- SQL DXP OM supporting Oracle and MySQL.
We have released SQL DXP SM as an early BETA for your review and feedback.
SQL DXP compares databases on different server platforms and can generate scripts
to make the source database generally the same as the target database regardless of
We say generally because not all SQL features are available between the different servers.
However tables and views are primarily consistent across all three servers.
SQL DXP will apply various translations to match data types and other SQL syntax rules
between the servers.
SQL DXP compares schema and data between the selected platforms.
Features in general for SQL DXP SM
Includes Schema Compare, Data Compare plus Schema and Data display
Compares the Schema and/or Data within a database.
Additionally SQL DXP can display the schema and data just like common database editors.
Supports MySQL Version 5.0 and higher plus SQL Server 2000 and higher
SQL DXP compares schema and data of either server type and generates update script
to make the target database equivalent to the source database.
SQL DXP automatically converts object elements of the source server type to match the syntax conventions of the target server type.
For example from SQL Server to MySQL SQL DXP will automatically remove the GO statement from stored procedures since this is not supported by MySQL.
Execute multiple projects simultaneously
Run two or more projects side by side in separate tabs, whether it's two schema compare projects on completely separate servers
or a schema compare and data compare project on the same server.
Because each process is run in separate threads you can be reviewing or even running an
update script while waiting for other compare processes to complete.
Project elements shown in Tabs
From editing a project, to displaying the schema compare results and then displaying the schema update script.
Each process is shown in its own tab. The usability of the application is much simpler and consistent.
Even using touch is easier with the new interface.
Generates single synchronize script ready for deployment
SQL DXP generates a single script including all of the selected objects and in the case of sub-selection can
automatically include dependent objects.
An example of dependent scripting is scripting the change to a single table however that
table has a dependent Foreign Key.
SQL DXP automatically includes the drop FK and recreates the FK at the end of the script.
Of course this is all optional but makes for significantly more reliable scripts, in the example without removing the FK
the script would fail.
Run change script from SQL DXP
There is no need to use another tool to run your update script, just click execute within SQL DXP
and the target database is updated.
Of course if you wish you can save the change scripts and use them in other tools,
perhaps you don't have immediate access to the remote server and you're comparing using a snapshot.
One or more filters can be applied to object loading.
An example is where a database has objects that are temporary (all begin with temp_) and not required to be compared.
Simply add a schema filter temp_ and these objects will not be loaded and compared.
The same can be done for columns within a table.
On Completion Events
Each project can execute a series of events once the initial project execution has completed.
The event could be to run another project, save a snapshot of the database schema,
run a report or execute the change script.
On Completion events are an easier way of defining tasks that were available only in command line processing.
Command line processing is still available however now uses On Completion events.
Built-in dependency management
SQL DXP uses both its own analysis of dependent items to determine object dependency for scripting.
Dependencies are important to reduce script failures and while these failures may not be catastrophic
(a second compare can be run and the database re-scripted) they do generally prevent a script from running in a single instance.
Perhaps a foreign key must be dropped before other changes are made or a function relies on a table.
SQL DXP without the html display is a single executable that less than 20mb.
There are no DLLs and no requirements to register COM, .NET or other services.
Subject to licensing, SQL DXP could be part of an in-house application without the complex installs and other requirements of other tools.
The html display for reports requires some third party DLLS and for MySQL and Oracle there is an option to use provider supplied DLLs.