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

DC6 RC1 - A few niggles, a bug and some bravos

1. The behavior appears to have reverted back to highlighting and positioning the list at the selected table in the list of "identical rows only" after syncronization (expanding the pane that was collapsed), instead of de-selecting and positioning the viewer at the top of the "tables or views with differences" pane (or somewhere meaningful to the User). It's a pain to be in the "wrong" pane...

2. In SQL Compare, if a "Refresh Comparison" is performed, the include-exclude check marks are left as-was before the comparison. In SQL DC 6 RC1 ALL difference checkboxes are checked after the initial compare AND every post-sync or manual refresh. Could you please "leave them alone" or allow us an option to say "check all differences" or "no action" in this regard. If I'm synchronizing in stages, with some manual updates between stages, my refreshes are there to see "now what's different among the tables of particular interest, i.e., those I've explicitly checked or un-checked".

3. Would like to be able to rename a comparison project in the "Comparison Projects" dialog box, much like adding a comment. This is important for cloned projects that had an IP addresss to reference the original instance, e.g. 10.150.3.228, where the IP is no longer relevant to the cloned project name.

4. Table dependencies are not adhered to. Not so much a niggle as a likely bug. I have FK constraints defined and enabled but DC6 ignores the "Insert parent records before children" requirement for fk's. This happened twice with this version on the same pair of tables in two different projects involving the same source but different target instances.

Love the PIVOT VIEW!

Like the flexibility of the WHERE Clause... The wood becomes visible from the trees!

Thanks for fixing the font-sizing Exception. DC5 became unusable today, so DC6 was just in time.

Thanks for a great tool.
PDinCA
0

Comments

1 comment

Sort by
  • Robert C
    Morning - and thanks for the comments!

    1. I've just checked this, and as far as I can tell, we try and reselect the object that was previously selected. If you open a project that doesn't contain a similarly named object, we don't select anything, but we do expand all the panes, I think.

    2. That's an entirely valid request - it's something we have considered, but it's not something we can get in for this release. However, it has been noted, so hopefully will make it into a future version.

    3. The easiest way of doing this is to right-click the project, click "locate on disk", then rename the file in Windows Explorer. However, I should warn you that in RC1, if you rename a project while the "comparison projects" dialog is open, it'll probably get upset :shock:. This has been fixed internally already, and should make it to the final release.

    4. I'm afraid I can't reproduce this one. I've just created a simple test database with a couple of tables with FK dependencies, and SDC does correctly order both inserts and deletes (delete from child before parent, and insert into parent before child). The caveat here is that if the target database is a backup, we don't take dependencies into account.

    Glad you like the pivot view - so do we :-)

    Thanks for the comments,
    Robert
    Robert C
    0

Add comment

Please sign in to leave a comment.