Way back, our server collation was set to Latin1_General_Bin to satisfy the requirement of some software running on that server. Since then, we've been using that server for other software that requires SQL_Latin1_GeneralCP1_CI_AS. Since most applications we now have use SQL_Latin1_GeneralCP1_CI_AS, I would like to change the server default to SQL_Latin1_GeneralCP1_CI_AS, and leave that 1 original DB as Latin1_General_Bin.
What's the best way to do this ?
John:
I have the same issue with one of my servers. The original use of the server was to host a datawarehouse generated from our mainframe.
However, overtime I've been asked to host several vendor applications which do not have the same collation.
I find it better to simply run an alter after the application insatll has setup the database. Or if the database is created from scratch, just use the drop down list and pick the desired collation.
USE master
ALTER DATABASE database COLLATE < collation_name >
"If it ain't broke....."
JerseyMo
Just an FYI for those attempting to use REBUILDM.
You need to be logged directly onto the console. It will not work via an RDP connection. Although, if you have access through a Lights Out interface, you may have success.
In SQL Server 2000 you don't need that, because you can add the collation to your create database and Table statement. Rebuild was a requirement for SQL Server 7.0. Hope this helps.
Kind regards,
Gift Peddie
I am not sure if you can use the list with SQL Server 2000 but the links below is the complete code page and collation listing for SQL Server 2005. Hope this helps.
http://msdn2.microsoft.com/en-us/library/ms144250(SQL.90).aspx
http://msdn2.microsoft.com/en-us/library/ms180175(SQL.90).aspx
I second (third) the trauma of different collations in tempd and operational databases. Its a right pain in the jacksy.
Backup your logins, and rebuild away.
Just remember there is a good chance that any database not in the server collation will suddenly start throwing errors...!
