How can we help you today? How can we help you today?

First impressions of the SQL Data Compare 6 Alpha

A couple of issues/suggestions:

1. I ran into an issue when comparing a Live Database to a Backup. The error was "Error mapping index key - try using clustered index as comparison key". The comparison stopped on one of the first tables in the list. First, why does the error occur and how do I change my configuration/options to address it? Second, can the comparison process continue working on the other table objects in spite of the error?

2. On the Project Configuration dialog box, it would be helpful if the grids on the Tables & Views and Remap Objects tab had resizable columns. I've got table objects and indexes with some l-o-n-g names. The grid on the Data Sources tab to select a backup file has resizable columns :-)

Keep up the good work,
James
jamessun
0

Comments

2 comments

Sort by
  • jamessun
    More thoughts...

    Can there be an option to ignore views when comparing a Live Database to a Backup? There's really nothing that you can do with them in this type of comparison, is there?

    Also, I really like the UI design, especially the Interactive Help bar; however, I've been trained to look for something like that on the bottom of the screen, not towards the top. Can you make that bar dockable or floatable?
    jamessun
    0
  • Robert C
    Hi,

    Thanks for the feedback.

    The "error mapping index key" is as a result of us not being able to find the clustered index key from a non-clustered index row. I wonder if you could take a look at your table's schema (in Management Studio or similar), and find out which columns your clustered index is defined on for that table?

    I'm expecting that there'll be a text column or two in there - in which case, are they n(var)char or just (var)char? Secondly, assuming that is the case, could you let me know what collation those columns are?

    A work-around for this is to select the clustered index as your comparison key (on the "Tables and Views" tab of the Project Configuration wizard). However, from our point of view it shouldn't fail in the first place on the non-clustered index!

    With respect to the other points you mentioned - all perfectly valid, and we'll see what we can do :-). I've logged them in the bug tracking system.

    Many thanks,
    Robert
    Robert C
    0

Add comment

Please sign in to leave a comment.