Generally liked the product. For an Alpha version, response times were good.
Editing a project and reloading the schema did take rather a long time though.
When going from "Comparison Projects -> edit, and pressing "save as", it's a bit confusing. Also, after hitting the "save as" button, when re-opening the project
the project just saved, the original location is the default chosen. Bit confusing
to leave the dialog open but with the only way out as a "Cancel" button. "Close" would make it more obvious.
Also, there are no tool tips on the buttons. Most are self-explanatory, but a new user (me), had no idea what the "Where clause editor" button
did until pressed.
Mapping Behavior. We have some "inherited" databases that (bizzarely) have been set up as case sensitive on some sites and not on others.
Unfortunately, in some of the case sensitive db's there is duplication of table names i.e. Customer and customer. Can't quickly compare a case sensitive
database agains non case sensitive version, since the "case insensitive" checkbox is for both databases. Not that usual a problem I guess!

Opening files. Is there any way we can specify a default folder (and other settings) in a config file?

There doesn't seem to be any way to compare when there are no indexes on tables.
Trying on a 2000 backup vs 2000 database with a single varchar field, and get no comparison keys. I know there should be keys/indexes on the
table in question, but it's not mine to alter. Is there any way (though it would be slow) to get around this?

In all, very good tool, like the ability to navigate (next/previous difference and the filters) and double click. Especially like the way a search for object filters the results of the comparison .
But for me, the ability to generate the sql is excellent, since we rarely get to connect to a live datase on a different network. At best we have backups
or "base data" initial databases.
andrewp
0

Comments

1 comment

  • Robert C
    Hi,

    Thanks for the comments.

    Reloading the schema: if you're using a backup, I'm afraid this can take a while. It's something we're trying to improve, but it's quite tricky since the schema information can be liberally scattered throughout the whole backup file.

    Default folder: I assume you mean for the project files? If so, it should be remembered between runs of the application - let us know if it isn't (or if any other settings you think should be persisted aren't).

    Comparing with no indexes: I assume you're comparing backups here? You're correct in saying there's no way of doing it if there aren't any indexes. To support this would be possible, but it'd be very hard to do this efficiently on large tables. It's not something that's going to be supported in 6.0, but we'll consider it for the future.

    I'm glad you like the new features, though - let us know if you hit any other problems.

    Thanks,
    Robert
    Robert C
    0

Add comment

Please sign in to leave a comment.