Error when calling ComparisonSession.CompareDatabases

RBohannonRBohannon Posts: 25
When I call ComparisonSession.CompareDatabases while comparing two database backups, I get the following error:

"No matching index was found for table Employee_Fingerprint"

Do all the tables have to have an index for SDC to compare them? How can I prevent this error?



  • Options

    When comparing backups, yes, you need to have some kind of index on the tables in order to compare them. This can be clustered or non-clustered, with clustered indexes generally giving superior performance (as you'd expect in SQL Server itself).

    Hope that helps,
    Robert Chipperfield
    Red Gate
Sign In or Register to comment.