Regresar
-
Título
"Cannot resolve the collation conflict between 'Latin1_General_CI_AS' and 'SQL_Latin1_General_CP1_CI_AS' in the equal to operation" errors in SQL Server agent -
Descripción
"Cannot resolve the collation conflict between 'Latin1_General_CI_AS' and 'SQL_Latin1_General_CP1_CI_AS' in the equal to operation" errors in SQL Server agent for numerous collections.
The error is similar to the following, however the collection names may differ.
ERROR [AGENTNAME-lowPriorityPool-2-[DBSS_Logical_Disks][YYYY/MM/DD HH:MM:SS]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSJdbcDiskVolumesProcessor processor of DBSS_Logical_Disks collection.
java.lang.RuntimeException: Failed to execute collection [DBSS_Logical_Disks], reason=Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.- -
Causa
The issue here is caused by collation differences in the database. Perhaps the database was attached from a different instance do the collation is different, or there are some columns that do not have the same collation. -
Resolución
Change the collations of the databases so that they are the same on the instance.
Note: Tempdb is created internally as a copy of the model database by SQL Server. If the model database's collation is changed, then when the tempdb is recreated it should also have the new collation.