February 2, 2006 at 2:44 am
Like sql2k, Sql2k5 has "new" default collations at installation time.
For what I understood, you could maintain support for the SQL2k en SQL7.0 collations SQL_**, but is it wize to do so ?
What would be a good reason to stick to the old collations ?
Is there any (performance) impact ?
We tend to keep all collations the same at one server, and if possible at each server with the same software-edition. Up until now we even succeeded in the latter one
Is there any advantage in planning a "collation upgrade" during the upgrade/migration process towards SQLServer 2005 ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 3, 2006 at 3:09 am
I know that with some operating systems, if you store data using a different collation from wher it is processed or displayed, this forces a collation conversion process. Even where source and target have a 1 to 1 mapping, the conversion process still gives an overhead. you can avoid this overhead by using the same collation for the client, the server, and the data.
However, the overhead involved in collation conversion is only a small part of the general overhead of running Windows programs. The effort involved in unloading data from old collation tables and loading it into new collation tables to avoid this conversion may well seem higher than the run-time overhead of doing the conversion.
I guess I am saying the answer to 'should we harmonise collations' is 'it depends'.
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
February 3, 2006 at 7:06 am
Don't forget to check the applications that access the data. Changing collation may "break" something in an application.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
February 3, 2006 at 7:13 am
Thank you for the replies.
For the moment, none of the applications has a specific need for a non-default collation.
The only way we may get into troubles is with our DTS-packages which perform #-server ETL, which may need to be adapted.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply