Skip to content

SCOM 2012 – Database collations, clearing things up!

August 22, 2012

Installing Operations Manager 2012 seems like an easy task, just click next, next, fill in some information and accounts and click finnish. Just make sure your environment meets the prerequisites and you are done!

WRONG!!

You probably have read (like me) the prerequisites a couple off times to make sure the installation is done in a proper way. The whole SQL collation part delivered me a headache and finally resulted in an escalation to MS.

Here is the story:

MS has decided that there should be support for Windows collations in the System Center Suite. Previous versions off Operations Manager required the SQL collation SQL_Latin1_General_CP1_CI_AS. In the supported configurations for Operations Manager (http://technet.microsoft.com/en-us/library/hh205990.aspx) is stated:

“SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation settings are supported”

This tells you that both database should have the same collation and lists the supported collations.

Wow, this sounds nice! My environment already has a SQL 2008 R2 cluster in place with the Latin1_General_CI_AS collation configured and have plenty off resources left so i can use this to install my Operations Manager databases on! I was affraid i needed to invest in new resources just because of the collation requirements!

Unfortunately after the installation i found that the Operations Manager DB indeed inherited the collation form the SQL instance but the Operations Manager DW DB did not and is created with the “old” SQL_Latin1_General_CP1_CI_AS collation.

So this means that running the installer makes my environment go to “unsupported”.
I also recieved many alerts after i loaded the Veaam nWork 5.7 management pack:

“Data Warehouse failed to deploy database component

Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “Latin1_General_CI_AS” in the equal to operation.”

When you run de Operations Manager installation the Data Warehouse database is ALWAYS set to SQL_Latin1_General_CP1_CI_AS, no mather what the SQL instance collation is. This leads to confilcts. Gladly MS has a work arround for this as described here: http://support.microsoft.com/kb/958979

What this means is that you cannot use any other collations at all.

Conclusion: ALWAYS INSTALL THE SCOM 2012 ENVIRONMENT ON SQL WITH THE SQL_Latin1_General_CP1_CI_AS collation!

Advertisements

From → System Center

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: