How do i install SQL Server 2005 on a German OS with SQL collation as SQL_Latin1_General_CP1_CI_AS.
(By default the collation is set as Latin1_General_CI_AS)
View Complete Post
Can anyone provide some insight into design techniques when multiple languages are required within SQL Server?
Let me tell you about our situation. We currently have a database that holds French content. New languages are going to be added (Chinese, Arabic etc.). We have to
make a decision to determine what would be the best approach to deal with all those languages.
Here are the approaches we identified:
I database per language:
We are attempting to change the default collation of an SQL Server 2005 Clustered environment. We have created an "unattended install" script to perform this, and have modified it several times as errors have arisen repeatedly. The last time, however, we
used the following script:
start /wait setup.exe /qb VS=<FQN of SQL Server Virtual Name> INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=<adminpwd> SAPWD=<NEW sa pwd> SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS SQLACCOUNT=<domain\user>
SQLPASSWORD=<pwd> AGTACCOUNT=<domain\user> AGTPASSWORD=pwd GROUP=SQL Group REINSTALLMODE=vomus
We are running this script from the primary (Active) node of the cluster. We did notice that the bootstrap logs created from this final execution did include logs from both nodes. When I look in the Summary.txt file, it tells me that Setup succeeded with
the installation. After the script executed, we rolled the cluster from primary to secondary, and rebooted the primary node. We then rolled the cluster back to the primary, and rebooted the secondary node. Once that was complete, we cycled the SQL Server service
from the SQL Configuration Manager. After all those steps, we opened SSMS client to look at the properties of master, and the collation was still CI_AI.
We are losing valuable time in
Did I miss something when running SQL 2008 R2 Setup.exe on Win2008 Server R2? I did not notice my opportunity to set the server collation to something other than my regional default. Was it on a tab that I missed?
Are my choices either (a) set collation at the OS level through Control Panel...Regional...Advanced, or (b) run setup.exe at the command prompt while specifying the desired server collation? Because I get that impression from reading this:
Have I read that correctly?
I tried two steps below separately: restricted user ran for 30 minutes then I stopped the execution; They obviously could not run simultaneously. I only want to operate at the database and not the server level. Our other key db is already in the desired
collation. We'd like to have equijoins work on tables with the same collation sequences, and not have to use ETL or individual ALTERs for each table involved.
Second point: is CP1 below a 2000 only collation? That appears to be a patently false assumption in another forum posting. It appears to be a valid 2008 R2 collation is the point.
ALTER DATABASE DBNAME
SET RESTRICTED_USER WITH NO_WAIT;
COLLATE SQL_Latin1_General_CP1_CI_AS ;
i have 2 data bases source(2005), destination (2008). i took a back up of database from 2005(SQL_Latin1_General_CP1_CI_AS) and restored in 2008(Latin1_General_CI_AS). now while running sp's, or any other queries, i am getting this error.
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
I donot want to re install my server as it is a big task , and i already restored DB's which are also a lot . so can anyone please sugegst a solution apart from the above two(reinstalling SQL, re-restoring DB's).
Collation is one of the most confusing features of SQL Server. BOL 2008 states that backward compatibility is the only reason to go with SQL collation. I thought previously it is just smart to stay with the default Microsoft offers unless there is a
real good reason to choose a different collation.
So is the default SQL_Latin1_General_CP1_CI_AS (Case Insensitive, Accent Sensitive) a good choice? (Assume the installation is brand new SQL Server 2008)
SQL Server offers the SQL_Latin1_General_CP1_CI_AS collation as the default collation for server installations.
For backward compatibility, the default English-language (US) collation is SQL_Latin1_General*.
we would like to update to SQL server 2005 or 2008. Now we are using SQL server express (several instances). Our databases have different collation.
Can we set up databases with different collation within one instance of SQL server 2005 or 2008?
My server collation is SQL_Latin1... as all my databases were upgrade from earlier version.
Should I plan a change to the collation to a window's based collation?