In SQL Server 2005 there is a new utility to compare the data in two tables these can be in different tables and different servers.
The utility will allow for the results of the comparison to be stored in a table.
It doesn't provide the details of whats different but whether a record is mismatched, only on the source or only on the destination.
The utility its Tablediff
Its located in the Program Files\Microsoft SQL Server\90\COM folder
From BOL:
The tablediff utility is used to compare the data in two tables for non-convergence, and is particularly useful for troubleshooting non-convergence in a replication topology. This utility can be used from the command prompt or in a batch file to perform the following tasks:
A row by row comparison between a source table in an instance of Microsoft SQL Server acting as a replication Publisher and the destination table at one or more instances of SQL Server acting as replication Subscribers.
Perform a fast comparison by only comparing row counts and schema.
Perform column-level comparisons.
Generate a Transact-SQL script to fix discrepancies at the destination server to bring the source and destination tables into convergence.
Log results to an output file or into a table in the destination database.
Look it up in BOL (
Denis The SQL Menace
SQL blog:
Personal Blog:
The utility will allow for the results of the comparison to be stored in a table.
It doesn't provide the details of whats different but whether a record is mismatched, only on the source or only on the destination.
The utility its Tablediff
Its located in the Program Files\Microsoft SQL Server\90\COM folder
From BOL:
The tablediff utility is used to compare the data in two tables for non-convergence, and is particularly useful for troubleshooting non-convergence in a replication topology. This utility can be used from the command prompt or in a batch file to perform the following tasks:
A row by row comparison between a source table in an instance of Microsoft SQL Server acting as a replication Publisher and the destination table at one or more instances of SQL Server acting as replication Subscribers.
Perform a fast comparison by only comparing row counts and schema.
Perform column-level comparisons.
Generate a Transact-SQL script to fix discrepancies at the destination server to bring the source and destination tables into convergence.
Log results to an output file or into a table in the destination database.
Look it up in BOL (
Denis The SQL Menace
SQL blog:
Personal Blog:
