Skip to content
← SQL Data Compare

How can we improve SQL Data Compare?

SQL Data Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Relaxed data type matching for comparisons

I'm using SQL Data Compare extensively as part of a refactoring project. As we optimize data types we end up with situations where we cannot compare source and destination table data due to mismatching data types. I'd like to request a flag that implements implicit/explicit SQL Server data type conversions. For example, I want to be able to compare and synchronize DATATIME/SMALLDATETIME to DATE or VARCHAR to TINYINT/SMALLINT/INT.

19 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jens Meyer shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Dave commented  ·   ·  Report

    Agreed! When comparing DATE vs DATETIME, even if the time part is always 0:00:00.000, it still says they don't match.
    In my case, the source database was a SQL 2005 database which didn't have the DATE type, and destination SQL 2016

  • James Shinevar commented  ·   ·  Report

    Agreed, there needs to be an easy way to compare DATETIME to DATE and tell it to forgo the actual time portion of the DATETIME. This happens so often when comparing data from different sources.