Search This Blog

Monday, March 23, 2015

SCCM SQL database not using right Collation

When installing SCCM 2012 R2 you might see this error:

Required SQL Server Collation

Configuration Manager requires that you configure your SQL Server instance and Configuration Manager site database (if already present) to use the SQL_Latin1_General_CP1_CI_AS collation, unless you are using a Chinese operating system and require GB18030 support.  For information about changing your SQL Server instance and database collations, see http://go.microsoft.com/fwlink/p/?LinkID=234541.  For information about enabling GB18030 support, see http://go.microsoft.com/fwlink/p/?LinkId=234542.

image

You can se the current SQL server Collation using this query in SQL Server management Studio

select SERVERPROPERTY('Collation')

image

To change server collation run setup.exe from the SQL Installation media again (in quite mode). In my example the command is:

D:\setup /q /action=rebuilddatabase /INSTANCENAME=MSSQLSERVER /SQLCollation=SQL_Latin1_General_CP1_CI_AS /SQLSYSADMINACCOUNTS=domain\administrator

SQL 2012 DVD is mounted at drive D

Rebuild System Databases

Before doing this please be aware that all user databases you might have will be dropped, so this will primary make sense on a dedicated SCCM SQL server without data!

image

Let check the collation again and yes it has been changed.

image

And now we don’t see any error about collation, but notice the new warnings about SQL configuration, that wasn’t there before.

When changing the collation all previously SQL configuration was lost, so you have to do this again.

image

No comments:

Post a Comment