During detection and information gathering stage of the migration, a fatal error occurs describing a collation conflict in a UNION operation.
The exact error message will vary from region to region. See below example:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Slovak_CP1250_CI_AS" in the UNION operation.
As fields were added to the database during Print Manager Plus 6.0, and 7.0 no consistent collation was set resulting in a variety of sorting rules. While they had little affect on the operation of Print Manager Plus 8.0, they do affect Print Manager Plus 9.0's greatly improved data integrity.
Collation: This is a setting used within text fields of the database to help determine sorting, comparison and equality.
Running the attached SQL Script will reset all of the collation to your system default making the Print Manager Plus 8.0 database importable. Because the import opens the database in a read only manner, it is best this be done manually. This also allows for backups to be performed.
- Backup your Print Manager Plus 8.0 Database:
There are multiple methods for doing this. The below article describes performing this backup when using the SQL Express option.
How to backup the Print Manager Plus SQL or Access Database
- Download and run the Attached SQL Script
This script has been designed to organize the collation to be consistent, and the same as the default for the database for all tables. Below is a link to our FAQ on editing and running scripts against the PMP 8 database, however let us know if you are unsure on doing this.
SQL Collation Script
Accessing the Print Manager Plus Database: See Section Named Running Scripts & Queries
- Rerun the Migration:
Once the attached script has been run against your Print Manager Plus 8.0 database, rerun the migration and it should proceed normally.