Author |
Topic |
terrence_chan99
Starting Member
12 Posts |
Posted - 2006-06-07 : 03:26:10
|
I have setting up a SQL Server 2005 machine in Australia and I use the SQL_Latin1_General_CP1_CI_AS as my database collation. I wonder what "default langage" should I use for user login? |
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2006-06-07 : 04:34:22
|
English... although a very lazy form of it...DavidMIntelligent Design is NOT science.A front-end is something that tries to violate a back-end. |
 |
|
terrence_chan99
Starting Member
12 Posts |
Posted - 2006-06-07 : 18:42:34
|
Can you explain why I should use "English" instead of "British English"? |
 |
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2006-06-07 : 18:49:06
|
Considering how the British founded and currently treat Oz, I would think that's fairly obvious. According to Books Online, the language setting helps with regard to date format interpretation and names. British and Australian dates follow the same format (dd/mm/yy) while (American) English uses mm/dd/yy. |
 |
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2006-06-07 : 18:54:18
|
>>Can you explain why I should use "English" instead of "British English"?Because Australia is not Britain?DavidMIntelligent Design is NOT science.A front-end is something that tries to violate a back-end. |
 |
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2006-06-07 : 19:14:27
|
What about strine ?Damian"A foolish consistency is the hobgoblin of little minds." - Emerson |
 |
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-06-07 : 19:14:29
|
quote: Originally posted by terrence_chan99 Can you explain why I should use "English" instead of "British English"?
The "English" setting for SQL Server really means American English, while "British English" is pretty much what it says.select name = convert(varchar(20),name), alias = convert(varchar(20),alias)from master.dbo.syslanguageswhere alias like '%English%'Results:name alias -------------------- -------------------- British British Englishus_english English(2 row(s) affected) CODO ERGO SUM |
 |
|
terrence_chan99
Starting Member
12 Posts |
Posted - 2006-06-08 : 00:36:48
|
according to robvolk, I should use "British English" as the date in Austalia is dd/mm/yy(same as British) but byrmol said I should use "English"... I am still not sure which one should I use.I think I should use "British English", however, as most of the software are from US.. I am not sure how it will affect each applications. |
 |
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2006-06-08 : 01:35:49
|
I wouldn't worry too much about it... No one in Australia does... I have seen both used in production databases and no ill affects...In hindsight I think you should pick the British English language as the date format is the same in OZ... Just make sure you use the ISO format for dates and the server won't care what variant of English you use....DavidMIntelligent Design is NOT science.A front-end is something that tries to violate a back-end. |
 |
|
|