The past
As we all know up to SCOM 2012 R2 the Collation Settings of the SCOM SQL databases was crucial and
ONLY SQL_Latin1_General_CP1_CI_AS worked, even though
Microsoft stated differently.
Main reason here was that the installer of SCOM installed the Data Warehouse database with this SQL Collation setting (
SQL_Latin1_General_CP1_CI_AS) no matter what (SQL) Collation Setting the SQL instance itself was running.
And when there is a mismatch between the (SQL) Collation settings of both SCOM SQL databases (OperationsManager & Data Warehouse) you could end up in situations like
these. Only a reinstall would solve that issue OR – when being blessed with really power SQL DBAs – the databases could be preserved while modifying the SQL Collation Settings.