SQL Delta Banner
SQL Delta Project Manager example
SQL Delta Duo For SQL Server
All of the SQL Delta Duo Compare tools compare schema and data of two databases. As the name says SQL Delta for SQL Server (SDSS) compares two SQL Server databases.

SQL Delta can also generate a synchronization script to update the target database making it the same as the source.
Features Overview

  • Includes Schema Compare, Data Compare plus Schema and Data display
    Compares the Schema and/or Data within a database. Additionally SQL Delta can display the schema and data just like common database editors.
  • Supports SQL Server 2000 through to 2016 and Azure
    SQL Delta works with all these versions of SQL Server, converting the schema to meet the requirements of the target server.

    SQL Delta re-formats the source to match the target when comparing databases on different servers making the display more consistent and generating less false positives compare results.
  • 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 Delta now 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 schema bound view.

    SQL Delta automatically includes the alter view (removing the binding) and recreates the binding 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 binding the script would fail.
  • Run change script from SQL Delta
    There is no need to use another tool to run your update script, just click execute within SQL Delta 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.
  • Schema Mapping (Object Owners)
    SQL Delta has always provided schema or owner mapping allowing you to map an owner from source to a different owner on the target.

    An example of this is you might have configured the database objects to use the default DBO owner and then you wish to move to a target server that has specific security and the owner TEST must be used.

    In SQL Delta all that is required is the source owner DBO be mapped to TEST and the resulting change script will update all of the objects.

    Even the contents of a stored procedure will be altered to reflect the ownership change.
  • Schema Filtering
    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 Delta uses both its own analysis of dependent items and the SQL Server dependency data 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 table relies on user defined type that relies on a function.
  • Small footprint
    SQL Delta 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 Delta 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.

Features of Schema Compare
SQL Delta Schema Compare example

  • Comprehensive Schema Display Filters
    Use filters to locate any text within the entire schema or hide objects of a specific type

    Even use persistent filters to check or remove the check of specific object before the change script is generated.
  • Generate Schema Snapshots
    Both Schema Compare and Schema view projects can generate a snapshot of the database schema.

    A Snapshot is an XML representation of the database schema and this file can then be stored with version control or just copied to another location as a schema backup.

    Even use snapshots to generate a schema from a remote database where SQL Delta cannot get a database connection.
  • Compare Schema Snapshots
    A SQL Delta schema snapshot can be compared with a live database or another snapshot to indicate changes between one version of the database and another.

    You can even use snapshots to create a version history and then if you need to revert to an older version just compare the older snapshot to the live database.
  • Schema Difference Reporting
    Generate a difference report showing the schema changes.
  • Export deployment script
    Deployment scripts can be saved to file for later deployment or in the case of updating a snapshot so the deployment script can be sent to the remote server and executed.
  • Deploy changes from SQL Delta
    SQL Delta can apply the change script directly to SQL Server without the need for external tools.

Features of Data Compare
SQL Delta Data Compare example

  • Table and Column Mapping
    Map a source table to a completely different table in the target database.

    Columns can also be mapped, even columns that have a different type however in this instance you will need to create a column transformation to ensure the data can be correctly scripted.
  • Apply Column transformations
    Columns can be transformed prior to the data load and compare.

    Any standard SQL function such as CAST can be used to alter the column data.
  • Data Load filters
    Apply row filter to the source and target data during load.

    Perhaps you have an extremely large number of rows in a table. Instead of comparing the entire table (which in part may have already been done) you can set a filter to compare a set number of rows.
  • Defined your own Key Values or use Primary Key
    Data compare requires one or more columns for sorting and identify key data.

    The Key data indicates if a source record also exists in the target. If not then the record has been deleted from the target or added to the target as the case may be.

    Generally we use the Primary keys as Key data however sometimes a table may not have a primary key or you may wish to devise your own compare and SQL Delta lets you specify any column(s) as a Key column(s).
  • Selective Column compare
    Mapped columns are including in the data load however only selected columns (all of them be default) are compared.

    This allows you to configure columns that may have data that you know is always different to be excluded from the compare however included when creating an update script.
  • Include Views in Data compare
    Views can also be included in the data compare.

    You can use a View plus mapping to transfer data from one database to another even though the tables may not contain the same columns and underlying table data is completely different between source and target.

    Of course it is best to have the target as a table since not all views are updatable.
  • Export results to file
    Data change scripts are automatically created as a file and these can be kept or automatically deleted.
  • Report on differences
    Report on the data differences between the two databases.

Schema View
SQL Delta always provided the ability to display the schema of a database or display the data without the need to run a separate application.

With version 6 we have overhauled this feature and provide a tree style display of the database schema and for tables and views a data view.

Schema View also has a script editor so you can run your own scripts against the database, whether these are scripts to display data or scripts that update the schema.

Even use SQL Delta to make changes to your source schema and then run a schema compare project to publish the changes to a target database. All done without the need for a separate tool.

What's Duo
Since version 1 SQL Delta has always performed Schema (structure) and Data compare within the one application. To us this was the most convenient and simple approach to take instead of having two applications perform common compare tasks.

Over the years customers have asked to separate the functions. Primarily they only ever ran one task such as Schema compare and never ran Data compare.

Soon we will be releasing SQL Delta Schema and SQL Delta Data which as the names suggest are stand-alone products. The stand-alone products will continue to feature the View mode so you can inspect your database, schema and data without needing to leave SQL Delta.