xSQL Schema Compare for SQL Server runs on Windows operating systems that have the .NET framework 4.0 installed.
Robust Comparison Engine - completely redesigned utilizing the experience gathered from over 30 thousand installations, and extensively tested for over a year, the new, platform agnostic, core database schema comparison and synchronization engine is very efficient, easily configurable, and scalable. Built on top of the core comparison engine, the SQL Server schema comparison and synchronization module supports on-premise SQL Server 2016, 2014, 2012, 2008/2008R2, 2005 and Azure v11 & v12.
Efficient GUI - the graphical user interface of the xSQL Schema Compare for SQL Server has been designed for speed - a context sensitive ribbon, action panels with clear descriptions and context sensitive menus provide multiple, intuitive, quick and easy paths for completing the database schema comparison and synchronization tasks in the minimum amount of time possible. The comparison results are displayed in a well organized manner on a highly customizable window making it very easy to see where the differences are and what it would take to push database schema changes from one database to the other.
One-click re-compare - xSQL Schema Compare for SQL Server maintains a comparison session history. A session is a persisted environment that contains all the data related to a comparison operation including databases and the respective credentials, comparison options, scripting options, execution options, included or excluded object types, included or excluded infividual objects and many more. It allows the end-user to repeat a database schema comparison with a single click. Application options control the way sessions are sorted and the max number of sessions that are persisted.
Customizable comparison sessions - comparing database objects is not simple, the answer to the question "is object1 equal to object2?" is not a clear cut yes or no, it depends. For example, two tables maybe be considered equal if we ignore the column collation but not equal if we consider collation, two stored procedures may be considered equal if we ignore character case but may be different if we consider the character case, two indexes may be considered equal if we ignore the fill factor but maybe different when we consider the fill factor etc. xSQL Schema Compare for SQL Server exposes over one hundred comparison options that give the user complete control over the comparison engine.
Cross version comparison and synchronization - you can perform a schema compare operation between SQL Azure v11 & v12 databases, SQL Server 2014 databases, SQL Server 2012 databases, SQL Server 2008 databases and SQL Server 2005 databases; the engine will compare the objects that are relevant for both sides of the comparison. The generated synchronization scripts are version specific – for example, if moving changes from a SQL Server 2012 database to a SQL Server 2014 database the synch script will be a SQL Server 2014 compliant script and vice versa.
Safe, standardized scripts - the database change script, that is generated based on the results of the schema compare, is wrapped into one big transaction to ensure that the database schema changes will either happen in their entirety or not happen at all. For every object that is affected by the change the scripts are organized in clearly defined sections, the set settings are properly initialized and the errors are logged and handled.
Schema snapshots - allow you to not only maintain a history (audit trail) of the schema changes, but they also provide a very efficient and safe way for reversing schema changes when necessary. Simply compare the database in question with the snapshot of itself, taken right before the changes were made and generate the script for reversing changes.
Unattended comparison and synchronization - the included xSQL Schema Compare Command Line utility allows the user to schedule schema compare and synchronization operations via the Windows Task Scheduler, SQL Server scheduler etc.