The primary function that the ignore option provides is reducing noise when comparing databases with different collations.
This helps keep comparison results focused on meaningful differences rather than collation mismatches. While this option also applies during deployments, it’s important to understand that it does not change the actual collation of any objects. Because of this, you may still encounter warnings about potential data loss if you are deploying between databases with different collations. These warnings typically occur when moving data between collations that could cause truncation or transformation.
If you receive such a warning, the safest approach is to pause the deployment and review the collation settings of both the source and target databases. Confirm whether the transfer will result in any unintended changes before proceeding. In cases where you are deploying to a scripts folder representation of a database rather than a live database, you can find the collation details in the RedGateDatabaseInfo.xml file located within the scripts folder.
Limitations
- Memory optimised table collation cannot be ignored
- User Defined Types don’t specify a collation, this is inherited from the database’s collation rather than being defined individually