February 17, 2010 at 8:00 am
We have consoladated a bunch of databases on to a new SQL 2008 server. There are a wide variety of collations involved, although usually Latin1 based. The differences in collation between the databases and the servers are causing issues with old code so we are looking at standardising the collations.
What are the pro's and cons of doing this? Assuming the same CI/CS and AS settings, and staying with Latin1 I cannot see an issue with this...
For example moving Latin1_General_CI_AS on to SQL_Latin1_General_CP1_CI_AS
TIA
Rob
February 17, 2010 at 9:04 am
because of different collation What type of issues you r facing did you found any Error Releted it.
Regards,
Shivrudra W
February 17, 2010 at 9:46 am
Hi,
it is when temporary tables are created because the server collation is different to the database collation. However, I've been looking at how to change the collation on the server and it is a pain. Changing the collation on the database looks easier but I'm not sure if changing the default then changes what already exists in the database, but I think not.
So... neither option looks like an easy option.
February 18, 2010 at 1:45 am
You can specify the collation at database level or table level, see BOL ---> COLLATE clause
February 19, 2010 at 6:59 am
The only way to change the database collation is to create a new db with the different collation and then move the objects and data into it. There is no easy way to change collations in an existing db.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply