Overview

Database operations (like attaching a database or upgrading its schema) fail due to collation mode conflicts. The store's debug logs show errors similar to:

Cannot resolve collation conflict for equal to operation.

Scenario example:

1. You run Microsoft SQL server A in collation mode SQL_Latin1_General_CP1_CI_AS.
2. The server fails.
3. You install Microsoft SQL server B, but in another collation mode (e.g. Latin1_General_CI_AS).
4. You restore a backup of a database that was taken from Microsoft SQL server A to Microsoft SQL server B.
5. This results in inconsistencies between the collation mode.

Environment

• GFI Archiver
• Using Microsoft SQL server as the database backend

Root Cause

The collation mode needs to be consistent throughout all components. If it is not, certain operations can fail. 

Resolution

Ensure that the collation mode is consistent throughout the server, the database, its tables, and columns. The suggested collation mode is SQL_Latin1_General_CP1_CI_AS.

For the scenario outlined above, it is needed to reinstall the Microsoft SQL server B in collation mode SQL_Latin1_General_CP1_CI_AS and restore the database from the backup once again.