Sql Server Data Compare Tools
TableDiff.exe should have everything you need. It is one of the. So you don't have to download anything.
• Table Difference tool allows you to discover and reconcile differences between a source and destination table or a view. Tablediff Utility can report differences on schema and data. The most popular feature of tablediff is the fact that it can generate a script that you can run on the destination that will reconcile differences between the tables. TableDiff.exe takes 2 sets of input; • Connectivity - Provide source and destination objects and connectivity information. • Compare Options - Select one of the compare options • Compare schemas: Regular or Strict • Compare using Rowcounts, Hashes or Column comparisons • Generate difference scripts with I/U/D statements to synchronize destination to the source.
TableDiff was intended for replication but can easily apply to any scenario where you need to compare data and schema. You can find more information about command line utilities and the Tablediff Utility in Books Online for SQL Server 2005.
A lot of tools are available for comparing database schemas and data. Over the years, I’ve worked with several comparison tools—however, I didn’t want to focus this review only on tools I’d used previously. I therefore reached out to the SQL Server community to get feedback on which comparison tools they’re using and would recommend. The resulting list of tools was pretty long. I decided to focus on four tools for comparing database schemas: Red Gate Software’s SQL Compare 9.0, ApexSQL’s ApexSQL Diff, xSQL Software’s xSQL Object, and Microsoft Visual Studio 2010’s Schema Compare tool. Test Plan I decided to use the AdventureWorks2008R2 database for the test runs because it makes effective use of a wide range of features that you don’t see in abundant use in most databases, such as multiple schemas, extended properties, Data Definition Language (DDL) triggers, XML schema collections, and full-text indexes.
Sql Studio Data Compare
Sql Server Database Compare Tools
I added some twists of my own to make testing more interesting and to see if I could break the tools: • I created a certificate in the database. • I created a stored procedure and signed it with the certificate. • I imported the certificate into the master database, created a login from it, and created a user in the AdventureWorks2008R2 database mapped to the certificate user. • I created an unsafe CLR assembly and a CLR procedure. • I changed the Trustworthy database property to allow the unsafe CLR assembly. • I created a Service Broker queue, route, and service, plus an event notification. • I chose an instance for comparing schemas without the full-text engine installed to force the full-text indexes to fail.