Top Features
Intuitive object model
A well thought out object model designed with the developers in mind, makes the integration of the schema comparison and synchronization functionality into your own .NET application easy and straight forward.
Fast, with a small footprint
We designed the schema comparison engine to be fast and efficient; you will be impressed by what Schema Compare SDK can do with minimum amount of computing and storage resources.
One of the key components of the Schema Compare SDK is our proprietary dependency algorithm; a great amount of experience and thinking has been materialized in the way SDK discovers and uses dependencies.
Tested extensively
We put every release of Schema Compare SDK through the paces in our own test lab - hundreds of scenarios and literally thousands of tests.
If something goes wrong, you as a developer have access to detailed error information and log files.
Cross version support
You can compare any version of SQL Server, on-premise and on Azure; the comparison engine will compare objects, properties and features supported on both sides.
The change script always honors the version and the compatibility level of the target database.
Schema changes report
Version 11 of the Schema Compare SDK includes a new schema changes report. The report is generated as an HTML file and provides on overview of the differences between two databases.
Filters built into the report help you navigate large schemas. You can show or hide objects, for example, by their comparison status, category, hide or show the definition of procedures, views, functions and more.
On-premise and Azure support
Schema Compare SDK supports on-premise SQL Server from 2005 through 2019 and the latest Azure Databases.
Over 100 comparison and scripting options
More than 100 comparison options give you total control over the comparison, scripting schema changes and synchr9onizing them.
Easy to deploy, with no dependencies on external libraries
While we are not condemning the practice of building applications that depend on external libraries (after all, our SQL Server database Schema Compare SDK is one such library) we believe that eliminating external dependencies
gives our database Schema Compare SDK two main advantages: it makes it easier to install and run, and it eliminates the “it's this other parties piece that is not working correctly” excuse.
