Schema Compare 4.2 release notes

What’s new:

The topic describes new features and improvements.

Support for MS SQL Server 2016 and its backup

dbForge Schema Compare for SQL Server now supports the new functionality of SQL Server 2016. Specifically, supported are:

  • Query Store providing performance-tuning capabilities allowing you to monitor queries, query plans, runtime statistics, and more.
  • Database Scoped Configuration allowing to configure the behavior of the application code at the database level.

Database Scoped Configuration supported

This feature gives you the ability to configure certain database parameters at the database level that before was only possible at a server level.

Improved synchronization logging

On the command line, the /log argument now sends the results of schema synchronization to a log file. Specifically, all errors and informational messages during the command line schema synchronization process are recorded to the file.

DROP IF EXISTS is used instead of DROP on MS SQL Server 2016

This command greatly simplifies routine operations and minimizes written code. What is more, if the object does not exist, you will not get any error and the execution will continue.

Integration into Microsoft Management Studio for SQL Server 2016 supported

dbForge Schema Compare for SQL Server seamlessly integrates into Microsoft SQL Server Management Studio 2016, so you can compare and synchronize SQL databases directly from the most recent SSMS version available.

Command-line client support for Version Control

This feature lets you automate source control operations for any source control system. A preset config file is provided for Plastic SCM and Mercurial (example). You can create your own config file using the Command Line Interacting option.

Synchronization options added

  • Use DROP and CREATE instead of ALTER
  • Add error handling statements to synchronization script
  • Transaction Isolation Level

New comparison options

Many new options were added to the schema comparison wizard so you can customize a comparison process to meet your specific needs.

  • Ignore user DEFAULT_LANGUAGE
  • Ignore Database Extended Properties
  • Ignore replication triggers
  • Ignore Replicated Tables
  • Ignore users’ permissions and role memberships
  • Ignore replication procedures
  • Ignore replication role
  • Ignore replication schema
  • Ignore INSTEAD OF triggers
  • Ignore database and server name in synonyms
  • Ignore Constraint System Names
  • Ignore DML and INSTEAD OF triggers present only in Target
  • Ignore indexes present only in Target
  • Ignore tSQLt Framework And Tests
  • Ignore sequences properties
  • Ignore next filegroups in partition schemes
  • Ignore Triggers State
  • Ignore Bound rules and defaults
  • Ignore WITH NOCHECK state on constraint
  • Ignore Foreign keys actions ON UPDATE and ON DELETE
  • Ignore NOT NULL Constraint
  • Convert UDTs into SQL Server basic datetypes
  • Ignore Table LOCK_ESCLATION
  • Ignore Semicolons
  • Ignore spaces in object names
  • Ignore object names in definitions
  • Associate column names having similar name options
  • Ignore Synchronization Script for Databases