Home > SCCM 2007 / 2012 > SCCM 2012: Required SQL Server Collation

SCCM 2012: Required SQL Server Collation

I had yet another SQL error at the Prerequisite Check page regarding the required SQL Server Collation:

Configuration Manager required 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 operation system and require GB18030 support.

The server collation is specified during SQL Server installation.  So this means that you need to re-install the SQL server or rebuild your database.  The server collation acts as the default collation for all system databases that are installed with the instance of SQL Server, and also any newly created user databases.

It is highly recommend to do this only on a SQL which is not in use by any other application!

Navigate to your SQL setup folder or DVD where the setup.exe is located and execute the underneath command:

Setup.exe /QUIET /ACTION=REBUILDDATABASE  /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=BUILTIN\Administrators

More info: http://technet.microsoft.com/en-us/library/ms179254(v=SQL.100).aspx

Advertisements
Categories: SCCM 2007 / 2012
  1. Steve H
    May 31, 2012 at 2:37 pm

    This note helped me with my SCCM 2012 Eval – Thanks!

  2. June 20, 2012 at 12:39 pm

    You’re a genius. Thank you. 🙂

  3. j0nbreen
    June 20, 2012 at 12:40 pm

    Reblogged this on theithelpdeskblog.

  4. Berwa
    July 4, 2012 at 8:36 pm

    Thank you very much, this is so helpful for me,
    I was about one week busy to resolve that problem……

  5. Rushikesh Kalyani
    July 5, 2012 at 7:52 am

    Thank you very much….!
    This post really helped me !
    🙂 🙂 🙂

  6. August 7, 2012 at 10:42 am

    Even after reinstalling a seperate instance with this collation correctly configured, I get the error. Any suggestions?

  7. Nino Iaccarino
    November 15, 2012 at 1:40 am

    i created another seperate sql instance and it installed fine after that. i did have to change the ports from dynamic to a static port for that instance.

  8. January 12, 2013 at 7:00 pm

    Thanks alot, this post has helped me resolve the problem..

  9. Ashvind
    March 24, 2013 at 11:10 pm

    thank you..worked perfectly

  10. nirmesh
    April 6, 2013 at 10:37 am

    Thank you very much solved my problem

  11. Rob
    April 30, 2013 at 12:00 am

    after the rebuild you have to reconfigure CLR:
    sp_configure ‘clr enabled’, 1
    go
    reconfigure
    go

  12. Kitaab
    July 5, 2013 at 4:51 pm

    I saw this after i completely rebuilt the SQL server Again

    I wish i had looked around before reinstalling SQL

  13. July 7, 2013 at 12:45 am

    Every weekend i used to visit this web page, for the reason
    that i wish for enjoyment, for the reason that this this website conations really good funny information too.

  14. Rajan
    July 12, 2013 at 4:01 am

    Thanks

  15. November 12, 2013 at 5:55 am

    Thanks, worked a treat

  16. Josh Harris
    February 21, 2014 at 1:21 pm

    legend

  1. No trackbacks yet.

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: