Shadow Baseline - COLLATION issues
Huzzer
Posts: 1 New member
Good morning all,
We are trialling the Flyway app and running into a couple of issues when creating the shadow DB.
1. For whatever reason (rightly or wrongly), some of our columns collations don't match the DB collation. Some SPROCs have temp tables which need joining to this column. To work, the collate on the temp table is set to match the column's collation. But the shadow DB baseline seems to ignore column/table collation and set's them all the DB one. Should this process be creating the table/columns with source collation? To make it an exact match after all?
2. When re-running a failed migration (e.g. due to the above), the rerun will always fail as even with a clean, some users remain and it keeps trying to add them again.
Any help, appreciated!
We are trialling the Flyway app and running into a couple of issues when creating the shadow DB.
1. For whatever reason (rightly or wrongly), some of our columns collations don't match the DB collation. Some SPROCs have temp tables which need joining to this column. To work, the collate on the temp table is set to match the column's collation. But the shadow DB baseline seems to ignore column/table collation and set's them all the DB one. Should this process be creating the table/columns with source collation? To make it an exact match after all?
2. When re-running a failed migration (e.g. due to the above), the rerun will always fail as even with a clean, some users remain and it keeps trying to add them again.
Any help, appreciated!
Answers
Please could you check if your project is set to ignore collation or not?
The setting is located under comparison options.
For additional context, there's more detail here https://documentation.red-gate.com/flyway/database-development-using-flyway-desktop/configuring-comparisons-and-script-generations/comparison-options/sql-server-comparison-options