|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Collation IssueHowever, no matter what we do it is setting the server collation to SQL_Latin1_General_CP1_CI_AS even though since the locale of the server is set to United Kingdom it should be setting it to Latin1_General_CI_AS. Indeed checking out an install of 32 bit SQL Server 2005 on a Windows 2008 32 bit Server it is indeed set to Latin1_General_CI_AS. So what is going on? Various web searches do not supply any details of this problem. This is driving us a bit mad really and is causing us to install SQL Server over and over again to try and fix. We've even tried setting the property SQLCOLLATION=Latin1_General_CI_AS via the setup.exe command line, but it still does not pick it up and also using the REBUILDDATABASES property fails. Can anyone help? Regards, Richard University of Bath Hello Richard,
During SQL Server installation wizard you will get "Collation Setting" page and in this page select radio button "Collation designer and short order:" in drop down do not change let it be "Letin1_General" now in Checkbox select "Accent - Sensitive" click next and complete the installation. Hope this will helpful. Cheers!!! Show quoteHide quote "faygate" wrote: > We are installing 64 bit SQL Server 2005 on a Windows 2008 64 bit Server. > However, no matter what we do it is setting the server collation to > SQL_Latin1_General_CP1_CI_AS even though since the locale of the server is > set to United Kingdom it should be setting it to Latin1_General_CI_AS. Indeed > checking out an install of 32 bit SQL Server 2005 on a Windows 2008 32 bit > Server it is indeed set to Latin1_General_CI_AS. So what is going on? Various > web searches do not supply any details of this problem. > > This is driving us a bit mad really and is causing us to install SQL Server > over and over again to try and fix. We've even tried setting the property > SQLCOLLATION=Latin1_General_CI_AS via the setup.exe command line, but it > still does not pick it up and also using the REBUILDDATABASES property fails. > > Can anyone help? > > Regards, > > Richard > University of Bath FM,
> During SQL Server installation wizard you will get "Collation Setting" page Thanks for this, however, this is something that we'd tried and that failed.> and in this page select radio button "Collation designer and short order:" in > drop down do not change let it be "Letin1_General" now in Checkbox select > "Accent - Sensitive" click next and complete the installation. I finally found a workaround for this:
> We are installing 64 bit SQL Server 2005 on a Windows 2008 64 bit Server. 1) Install 64 bit SQL Server 2005 but do not carry out any post installation > However, no matter what we do it is setting the server collation to > SQL_Latin1_General_CP1_CI_AS even though since the locale of the server is > set to United Kingdom it should be setting it to Latin1_General_CI_AS. tasks 2) Install SQL Server SP2 3) Run the command: start /wait setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=************** SQLCOLLATION=Latin1_General_CI_AS 4) Force a re-install of SQL Server SP2 5) Carry out any planned post installation tasks. It's a bit of a pain, but it does work. If anyone from Microsoft is listening I'd still be interested in why this problem occurs on the 64 bit edition but not on the 32 bit version. Thanks. Richard. Nice to know Richard finally you make it :)
Yes, this is someting interesting.... through command line it worked :( Show quoteHide quote "faygate" wrote: > I finally found a workaround for this: > > > We are installing 64 bit SQL Server 2005 on a Windows 2008 64 bit Server. > > However, no matter what we do it is setting the server collation to > > SQL_Latin1_General_CP1_CI_AS even though since the locale of the server is > > set to United Kingdom it should be setting it to Latin1_General_CI_AS. > > 1) Install 64 bit SQL Server 2005 but do not carry out any post installation > tasks > 2) Install SQL Server SP2 > 3) Run the command: > > start /wait setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine > REBUILDDATABASE=1 SAPWD=************** SQLCOLLATION=Latin1_General_CI_AS > > 4) Force a re-install of SQL Server SP2 > 5) Carry out any planned post installation tasks. > > It's a bit of a pain, but it does work. If anyone from Microsoft is > listening I'd still be interested in why this problem occurs on the 64 bit > edition but not on the 32 bit version. > > Thanks. Richard.
Other interesting topics
Access 2000 or 2003 project - can it connect to sql server 2008?
How to look for values in a table SQL2005 spaces in T-SQL An error occurred during the execution of xp_cmdshell. A call to 'CreateProcessAsUser' failed with e the alert couldn't send an email Downloading Query Analyzer? performance question - high cpu usage 16GB memory for SQL Running Total i3 symantec tools for sql server |
|||||||||||||||||||||||