Comments
3 comments
-
Hi,
When you mention the PK requirement, do you mean in general or for comparison to backups?
The requirement for backups is that there must be some index defined on the table - it doesn't have to be a primary key, though if it isn't, you'll need to select it by hand (in the Tables & Views tab of the project configuration wizard). For live database to live database, you can choose any old comparison key, though those that have matching indexes will be faster.
Out of curiosity, were the backups you tried originally in LiteSpeed's format (then extracted using their decompression tool), or were they just native SQL Server backups from the start?
I've noted the feature request for the Excel export, though I can't promise anything at this stage, I'm afraid.
Many thanks,
Robert -
Regarding the PK requierment, I meant in general. Thanks for the info on the comparison. Our backups are originally in LiteSpeed's format. I'm assuming there is no support for this, correct?
Thanks!
Paul -
Hi Paul,
Yes, you're correct, there's no support for Litespeed directly, I'm afraid. I was just pleased to know it worked having been converted back into native MTF format.
Thanks,
Robert
Add comment
Please sign in to leave a comment.
We use SQL LiteSpeed for our backup compression, so we don't have any RedGate compressed backups to work with, but the uncompressed backup comparison works very well!
Another option nice to have would be exporting each table as a different sheet in an Excel document for ease of management!
Thanks!
Paul