Not matching identity columns as comparison key

PaulOckendenPaulOckenden Posts: 8 New member
edited September 12, 2016 5:48AM in SQL Data Compare 11
Where tables have no IX or PK, I'd assumed that SDC would pick an identity column (if one exists) to match on. Especially if the "include identity columns" option is ticked.

But it seems this isn't the case.

Is this the expected behaviour? If so, I'm going to have to manually set the comparison key on several hundred tables.

Thanks,

P.
· Share on Twitter

Comments

  • Eddie DEddie D Posts: 1,802 Rose Gold 5
    Hi, thank you for your forum post.

    This is expected behavior. To match rows in the two data sources, SQL Data Compare requires a comparison key for each table or view. SQL Data Compare automatically selects a comparison key when:
      •tables contain a matching primary key, unique index, or unique constraint •views contain a matching unique clustered index

    As per this INFORMATION in the help documentation.

    Sadly a column that uses the IDENTITY keyword is not enough, so will mean that you need to manually set a custom comparison key, sorry.

    Many Thanks
    Eddie
    Eddie Davis
    Senior Product Support Engineer
    Redgate Software Ltd
    Email: support@red-gate.com
    · Share on Twitter
Sign In or Register to comment.