SQL_LATIN1_GENERAL_CI_AS -> SQL_LATIN1_GENERAL_CP1_CI_AS help

[gvlaarho]

Hi all,

I must implement an sccm 2012; the company wants that i use the existing SQL server 2008 r2. The problem, this one is configured in SQL_LATIN1_GENERAL_CI_AS instead of SQL_LATIN1_GENERAL_CP1_CI_AS as collation; what can i do ? Is it possible ?

 

Many thanks in advance

[Geniegl]

im also looking for the answer, did anyone has solution for that ?-)

[GarthMJ]

No, it must be the exact SQL collation listed within the setup.

[anyweb]

you can reinstall SQL, read here for more details.

 

http://www.niallbrady.com/2012/03/13/about-to-install-configuration-manager-2012-check-your-sql-collation-first/

[Peter33]

You can change the collation with this command.

 

setup.exe /ACTION=REBUILDDATABASE /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS /INSTANCENAME=MYINSTANCE

[Rocket Man]

I may be wrong on this:

 

Is it not possible to create a new instance on the already existing SQL server for the SCCM DB and have the proper SQL collation on this? It is recommended to have a dedicated SQL server for SCCM but if your enviornment is only light then this could be an option if it works!

 

Maybe I am wrong but whenever I set up 2 instances, one for the configMgr DB and one for WSUS, I could choose the collation on both and have different collations if I so wished!

Does an instance not have it's own DB engine seperate from other instances that reside on the same SQL setup??

[GarthMJ]

Maybe I am wrong but whenever I set up 2 instances, one for the configMgr DB and one for WSUS, I could choose the collation on both and have different collations if I so wished!

 

Was this just for testing? You don't need two different SQL instances for WSUS and CM. They can exist on the same instance.

[Rocket Man]

Hi Garth

 

Yes I do know that both roles can reside on the same instance, but in production it is recommended to use 2 seperate instances to host the configMgr DBs and the WSUS DBs.

Apparently it is easier to rectify problems if they arise if they are on seperate instances!!

 

But just for the circumstances above(I see this an old post now and is probably of no use as it is more than likely sorted by now), would this have not been option? I am not a SQL person but I do remember been able to choose a different collation on the separate WSUS instance, so that to me means that the the same 2K8R2 Sql server could have been used if a new instance was created??

 

Rocket Man

[GarthMJ]

I have never see (or heard) that recommendation before, Where did you see that?

Personally, I would never recommend have different SQL collation between WSUS and CM db. It would most likely work but it would seem to me that it would cause unnecessary translation from one collation to the other.

[Rocket Man]

 

I would never recommend have different SQL collation between WSUS and CM db

 

Hi Garth

 

I think you have misunderstood me.

I do have seperate instances at some of my sites, but they are both the same SQL_Latin1_General_CP1_CI_AS!!

The point I am trying to get across for the purpose of this thread, would it not have been possible for gvlaarho to create a new instance on his already exsisting SQL 2K8R2 server and specify it to have a SQL_Latin1_General_CP1_CI_AS collation. I feel the answer is yes due to me been able to specify a different collation for the WSUS instance(which I specified to be SQL_Latin1_General_CP1_CI_AS) the same as my configMgr instance collation!!