Data Compare for SQL Server

What is Data Compare for SQL Server?

Data Compare for SQL Server lets you compare and synchronize data in SQL Server databases. You can use it for data migration, auditing, replication verification, filling development databases with production data.

Data Compare for SQL Server supports SQL Server 2000 through 2019, Azure SQL Database and is available for free as a fully functional Lite Edition (see "Editions" below).

Overview

Lights

• Compare data across two SQL Server databases, tables, and visualizations
• Custom mapping of database tables, visualizations, schemas, and data types
• A simple and efficient user interface
• A workspace that stores settings, comparison sessions, with support for one-click comparison
• Map rows of data using built-in keys and unique indexes, or create your own custom keys
• Compare entire tables or part of them, selected through custom where clauses
• Variable size of batch and transaction
• Command-line tool, including a wizard for creating and managing command-line configuration files
• Compare SQL Server 2000-2019 and Azure SQL Database on-premises

Requirements

xSQL Data Compare for SQL Server runs on Windows operating systems that have the .NET framework or higher installed.

Resources

Comparison mechanism - The robust and highly efficient comparison mechanism compares millions of rows quickly, while tightly controlling resource utilization. There is no technical limit on the size of the databases that SQL Server Data Compare can synchronize.

Modern GUI - The Data Compare for SQL Server GUI  reflects the latest patterns in UI design. Context-sensitive ribbon, action dashboards with clear descriptions, asynchronous implementation of time-consuming operations, detailed progress information, and more.

One-click comparison - Data Compare for SQL Server maintains a history of comparison sessions. A session is a persistent environment that contains all data related to a comparison operation, including databases and their credentials, comparison options, mapping rules, deleted objects, and more. It allows the end user to repeat a comparison with a single click. The options control how sessions are sorted and the maximum number of sessions that are maintained.

Custom mapping - The mapping rules feature lets you customize the way SQL Server database objects are paired. Mapping rules include: "Schema mapping rules" that determine how database schemas are mapped; "Name mapping rules" that determine how the names of database objects are mapped; and "Data mapping rules" that determine how sql data types are mapped.

Custom comparison keys - Do you want to compare tables or database views, but are they shown as non-comparable because there are no primary key or unique indexes defined in them? After xSQL Data Compare for SQL Server analyzes the database schema, you can define a unique key (any combination of the columns in this table) to use in sql data comparison. The lines will be paired based on the selected key.

Command-line utility - The included command-line utility, highly configurable, allows you to schedule data comparison operations through the Windows Task Scheduler, SQL Server Scheduler. A step-by-step wizard helps you create and manage the configuration files used by the line command, generating consistent and always-up-to-date xml files.

Full control over comparison and synchronization - a wide variety of options provides granular control over the behavior of the sql database comparison engine. Comparing database visualizations along with sql database tables, analyzing table dependencies, and organizing the t-sql synchronization script accordingly, comparing sql databases with different collations are just some of the options available.

Manipulating large databases - custom algorithms handle the serialization of data lines and t-sql script fragments as needed, ensuring strict control of memory usage.

Script execution engine - The intelligent and proprietary script execution engine ensures that very large t-sql scripts, including scripts for binary columns and large text columns, run successfully, providing continuous progress information and allowing the script to be safely disruptive if necessary.

Error handling - systematic error handling aims to eliminate unexpected/unexplained results. Non-critical errors are logged and reported, but do not interrupt the operation. Errors are reported through dialog boxes or printed in the output pane. A full error log is created.

System requirements:

CPU: 1.8 GHz dual core processor

RAM: 2 GB

HDD / SSD: 50 GB of free space on the main drive

Operating system: Microsoft Windows 8 32-bit, Microsoft Windows 7 32-bit and Microsoft Windows Vista 32-bit

Resolution: 1024×768