What's New

SQL Delta Version 6 is vastly different to version 5. The product version numbers have also been aligned so that all SQL Delta products are Version 6.

The following are some of the more significant changes from 5 to 6: 

  • Multi-tab user interface, now multiple projects can be run simultaneously without blocking the user interface.
    For example a long running data compare can be running while viewing a completely different database schema on a separate server.
  • Separate Data Compare projects, the data compare is now a self contained project and schema compare is not required.
  • On Completion Events allow post compare actions to occur without the need for user intervention. This replaces manual editing of the project for command line.
  • Schema View Project is similar to the old single mode where the schema of a database is displayed.
  • Project Manager and Project Groups, now projects are edited within a separate tab rather than in-place. Projects can also be grouped under and group name.
  • Schema compare results can be displayed in difference styles including grouped by object type or by difference.

Data Compare now Stand-Alone Project

We have moved the data compare from part of the schema compare process into a stand alone project. Data compare was a project within a project using a wizard to define the project configuration. By making data compare a project of its own we can now have a single project editor to manage the project details. It is true that the new data compare project is more complex however it's also more feature rich with the ability to map differently named tables, even differently name columns can be mapped. We also now provide the ability to run pre-load data conversions so data of different types can be compared and synced.

From feedback we have received we understand that a common process was to run the schema compare, update the target schema to match the source and then configure an run the data compare. This same process can still be achieved by creating two projects, schema and data compare and optionally using On Completion events to automatically execute the sync script and then run the data compare project. Alternatively run the schema compare and then manually run the data compare project. The settings within data compare provide for automatic inclusion of any new objects saving time manually configuring the data compare project.

On Completion Events

In Version 5 the command line process could perform a number of actions automatically such as running the sync or generating a report. Unfortunately not everyone knew about these features and they were not easy to configure since changes had to be made directly to the project file outside of SQL Delta. In version 6 we have made these features now available within the project definition as part of On Completion Events. Now you can run multiple projects in sequence and create actions that occur once the project has run. Some examples for on completion are:

  • Run a target schema view project and using On Completion generate a snapshot of the schema, effectively backing up the schema. Then on completion runs the schema compare project and automatically performs the schema sync.
  • Configure three separate schema compare projects each with on completion save and email the sync script to a central location to store for audit.

All the features that previously only existed within command line are available and are easily configured within the project. There should no longer be a need to manually modify the project file.

Schema View Project

A schema view project creates an editor like environment for working with a specific database. The database objects are displayed in a tree view and the elements of each object such as table or view are displayed as either a DDL representation or in a grid display. Additionally the data of a table or view can be displayed. Use schema view to create ad-hoc scripts to display or update data or even modify the database schema.

The schema view is particularly handy for evaluating a database that is also being compared. You might want to execute various scripts against the database, display data from tables, to help understand schema differences and impact of potential changes to the database prior to deploying the script. While this can be done with another tool such as Management Studio we have found by simply duplicating the compare project, changing it to schema view and running the details of the database are immediately available and running various queries quick and easy.

New Project Editor

In version 5 we had some feedback indicating there was some confusion between global project options and local project options where the global options were mostly defaults and the project options affect the specific project. Given the design of the project editor in version 5 this confusion was not easy to remedy. Also with the new stand-alone data compare project there are more options available and these are better contained within a central edit project view.

We have simplified the project creation and editing process into a single dedicated edit project view, displaying options and features specific to the project type. Additionally both the edit project and project results can be displayed in separate tabs allowing quick changes to the project settings to observe the effect on compare results.

The new project grouping in the project list provides a way of combining like projects together in one section within the main project manager list.

Schema Compare Changes

The schema compare now has object grouping as part of two new display modes. Now objects can be grouped by type of difference or by object type and the groups can be collapsed to hide or show certain groups. 

The object results now by default display the SQL text tab first instead of status and then a column, index and so on display. These tabs can be repositioned and this state saved per project.

Triggers are now scripted as part of the object instead of shown as a separate object. This was changed to reflect that nature of a trigger since it cannot exist without a primary table or view.

All new filters provide a high level of display filtering plus pre and post checking of objects to be included in deployment scripts.