Different Collation setting for Project Server Dbs & WSS Content D

[waqas sarwar]

Hi Guys,

I am now a days fall in a problem and could not understand what it is.

We are running a WSS 3.0 & Project Server 2007 envirnoment. Our envirnoment
is upto date till April commulative updates, we did not install the SP2
yet.We are seeing different Collation used for Project server Database and
for Content DataBase.

Sql Server 2005's deafult Collation is: SQL_Latin1_General_Pref_CP850_CI_AS

Project Server 2007 Using the(all 4 Dbs): SQL_Latin1_General_Pref_CP850_CI_AS

WSS Content Db Using: Latin1_General_CI_AS_KS_WS


We recentlly build in a new production envirnoment with 2 Database server
and 3 Web Front end and 2 App server.

Same problem we can see over their.But here is little change, the Datbase
deafult collation is different from the our old envirnoment.

Sql Server 2005's deafult Collation is: SQL_Latin1_General_CP1_CI_AS

Project Server 2007 Using the(all 4 Dbs): SQL_Latin1_General_CP1_CI_AS

WSS Content Db Using: Latin1_General_CI_AS_KS_WS


So please update, either its a issue or the SQL server work in the same way.
Different DB collation for the Project Server and different for the WSS
content DB.
1 thing Project server DBs are using the SQl Server's default collation but
WSS using its own.

Tell me is it risky, i have to change the collation and make it similarl for
all. if yes then how can i change it, or its ok. Please possible to refer to
some posts.

 

[Martin Laukkanen]

I can't say I've ever looked into what codepages are used by the WSS
databases in specifically and how they are set, but I do know that Project
will provision the databases using the SQL default, which is clearly
happening in your environment.

Based on the codepages in use on your SQL server you may encounter problems
as your project server databases (and sql default) does not include the
required properties KS and WS (Kana-sensitve and Width-sensitive). HOWEVER
from experience I have seen all manner of incorrect collations used, and
AFAIK as long as you get the first two right CI & AS (Case-insensitive and
accent senstive) then it should work.

I would not recommened trying to change the collation as simply changing it
does not go through and actually change any of the data that may have been
created based that collation. Unfortunately if this is really your issue
provisioning new databases with the SQL default correctly configured is the
recommended course of action.


Hope that helps,

Martin