October 11, 2006 at 8:50 am
My company are just about to go international...
They also want to keep everything in one database despite the fact we'll be taking things in Polish/English and Arabic.
As far as I can tell SQL Server 2005 will handle having fields with different character sets in it as long as that set is installed.
Are there any pitfalls I should keep an eye out for that anyone has heard of?
October 12, 2006 at 3:34 am
If you are using different character set code pages, then you should be OK. If you use different collation sets then ther aer a few things to look out for.
If you are using a collation set that is different to the SQL instance collation set, you can have issues when tempdb gets used. Any #temp tables by default will have the system collation set, but you can specify your own collation when the table is created. Any workfiles will always and only have the system collation set.
This can cause problems if you are trying to join a column with collation set a in your application DB with a #temp table with collation set b. There is additional syntax (see BOL) you can use to force the join operation to use a given collation set.
If you have control over the SQL used, you can get round any problems caused by mixing collation sets within a SQL instance. If you have a vendor product that generates its own SQL then mixing collation sets is harder to deal with.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply