August 6, 2009 at 5:26 pm
Hi,
We have SQL Server 2005 EE 64 bit with SP3 and it is A/A/P cluster setup. On Node1, we have sql server 2005 EE 64 bit having SHARE POINT Databases.
When we installed SQL Server, we selected the default collation settings "SQL_Latin1_General_CP1_CI_AI" and later we came to know that Share point installs share point databases with collation settings "Latin1_General_CI_AS_KS_WS"
So now we left with the following"
System databases collations: SQL_Latin1_General_CP1_CI_AI
Share point databases collations:Latin1_General_CI_AS_KS_WS
I went through this link
http://www.myriadtech.com.au/blog/James/Lists/Posts/Post.aspx?List=64361d17-3348-480d-934c-a4fbfd951a71&ID=25
and its telling that we need to choose Latin1_General_CI_AS_KS_WS NOT SQL_Latin1_General_CP1_CI_AI while installing SQL Server 2005 for Share point application.
And also the above says we will get collation errors in the error log as below:
This problems comes up from time to time when you try and install MOSS or WSS you might get the following message in the event log:
Error thrown to event log
---------------------------------------
The SQL Server collation on SQL Server instance ServerName\InstanceName
is not supported. Windows SharePoint Services requires a Latin1 General
dictionary order, case insensitive, accent sensitive, kana sensitive, and
width sensitive collation (SQL_Latin1_General_*_CI_AS).
But we NEVER get any errors so far
Now I want confirm with the forum experts and DBA's maintaining share point databases that what collations you have?
Please see the attachment and confirm the collations should be as in Fig:1 OR Fig:2 considering Share point Application
If we must need to change the collations of system databases to Latin1_General_CI_AS_KS_WS from SQL_Latin1_General_CP1_CI_AI in order to match Share point databases, what are the steps I need to follow.
Please consider that Its a Clustered Environment. I asked this before also But I did not any confirmation which collation to use.
Thank You
August 6, 2009 at 8:44 pm
This Collation is also used by SSRS which does not care what is your server base Collation however I think in SharePoint you are required to use that Collation for the server. Check below for the SharePoint database guide.
Kind regards,
Gift Peddie
August 6, 2009 at 9:36 pm
We now have a couple of dedicated servers for MOSS 2007. When I installed SQL Server on hose servers I used Latin1_General_CI_AS_KS_WS.
We also have a WSS setup on a development server where we first started working with WSS as a POC/Department Site. That server has SQL Server installed Latin1_General_BIN2 and we have had no problems with WSS on that server.
If you are setting up a dedicated server or instance for WSS 3.0/MOSS 2007, I'd use the same collation the it wants.
August 8, 2009 at 12:38 am
Hi Lynn,
I went through this link http://www.dbforums.com/microsoft-sql-server/1627384-moss-collation-question.html in which one of the forum members telling the below
Hey guys,
I am working on the database side of an upgrade for our Sharepoint site to MOSS 2007. The current environment is SQL Server 2005 (SP2) clustered (8 dual core CPUs, 32GB RAM) with about 0.75 TB of data (about 10 different dbs). I noticed that the collation on the sharepoint databases are not the same as the system databases and other user databases.
The collation setting for our current Sharepoint is:
Latin1_General_CI_AS_KS_WS
The collation setting for MOSS is:
Latin1_General_CI_AS_KS_WS
The collation setting for our system databases is:
SQL_Latin1_General_CP1_CI_AS
The collation setting for the server is:
SQL_Latin1_General_CP1_CI_AS
I am aware of the following issues with having different collation settings between user databases and system databases.
http://sqlblogcasts.com/blogs/tonyro...07/12/883.aspx
http://support.microsoft.com/kb/843578
Currently nothing is broken, everything is working fine; So my question is:
What does best practices suggest I do in this situation?
Do I leave everything as is? Do I change the server collation and system databases?
Any suggestions and feedback will help.
Thanks,
Reghardt
I'm also in the same situation, our share point application is also in production from several months and I did not see any problem with having collation for system databases and share point different as mentioned above.
So in current situation what decision should I take?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply