Use the Collation different to server health check in Mini DBA to review Azure SQL Database configuration, metadata, and monitoring signals before they become active alerts.
This check identifies a database whose collation differs from the logical server or expected application collation.
Different collations can change sorting and comparison behaviour and can cause collation conflicts when queries join strings across databases or temporary objects.
Confirm whether the difference is intentional. Before changing a database collation, review its effect on string comparisons, joins, temporary objects, indexes, application SQL, and migration effort. Test any change through the normal database change process.
Record the current and expected collations, affected applications or cross-database queries, observed conflicts, and the decision to change or retain the configuration.
Prioritize it when users see collation-conflict errors or when a migration or application depends on consistent string behaviour. An intentional difference can be documented as an exception.
Define the expected collation when provisioning databases and include it in deployment checks for applications that use cross-database queries.
Document the expected collation, approved exceptions, affected applications, and the process for handling collation conflicts.