Why are tables considered different?

fredrikg

What could cause SQL Data Compare to treat two "identical" tables different, so that the automatic mapping doesn't work?

I am trying to use the command-line options to synchronize data between a set of tables from a SQL Server 2000 database to a SQL Server 2005 database. I create the tables manually in the target database, using the exact same script as for the source database.

The problem is that SQL Data Compare doesn't think the tables are the same. Using the GUI I could manually map the tables together, but this is not possible using the command-line.

Interestingly, it works fine if the two databases are on the same SQL Server 2000 database.

So, what could possibly be the reason for this?

Many thanks!
/Fredrik

Linda Hawksworth

Unfortunately, you have come across an issue that was introduced in SQL Data Compare 7.1. This is being worked on by the development team and we are expecting a patch by the end of next week. Apologies for the inconvenience. I will let you know when the patch is released.

Linda Hawksworth

This patch has now been released. I'll send you the link in a PM.

carlos.oliboni.amigo

Hello Linda,

my version of SQLDataCompare is the 7.1.0.245 and it always worked fine till now, because I only used it by the GUI. Now I am automating the building process of some projects we have, and it brings the need of running SQLDataCompare through the command line interface. The problem I am facing seems to be the same fredrikg had.

How can I get this patch, if it is the case?

Thanks in advance,
Carlos Amigo

Linda Hawksworth

I'll send you a PM with the link to the patch.

carlos.oliboni.amigo

Hello Linda,

the patch you sent me solved the problem I was facing. Thank you so much!

Yours,
Carlos Amigo