Comments
Sort by recent activity
Additional info - if I look at the comparison keys on the tables before running the scan, this table is mapped on the one index on the table. / comments
Additional info - if I look at the comparison keys on the tables before running the scan, this table is mapped on the one index on the table.
Hi Pete,
Thanks for the reply. As stated, I am using SQL Server native compressed backups, not RGs proprietary backup.
I have only generated my data sources from scratch, creating a new project each time I have attempted. I have not ever had a successful synchronization, so I have not had a project worth saving. If I can get the software figured out, I will likely always run it from the command line; the syntax of which I just finally found after extensive unsuccessful testing through the GUI. It sounds like you are telling me that the object that is not instantiated is the comparison key - basically, I am getting to a table in the comparson that doesn't have a comparison key, so it is failing. Is there a way to ignore this error and continue, e.g. to perform a full table scan instead of comparing on keys, or ignore the table all together?
It sounds like my database structure ( I do not engineer this database and have no control over adding key constraints) is unsupported. Does this sound accurate?
The direct DB to DB fails at a random place each time - is it possible this is due to table locks being placed by the table being in use? What is the timeout value?
I was able to get a good comparison (DB to DB) just now using the compare checksum option. Can I make this default, or specify it from the command line? I notice this option is not available from backups. / comments
Hi Pete,
Thanks for the reply. As stated, I am using SQL Server native compressed backups, not RGs proprietary backup.
I have only generated my data sources from scratch, creating a new project ea...