Skip to main content
Tweeted twitter.com/StackDBAs/status/714221499402551296
edited tags
Link
Paul White
  • 90.3k
  • 30
  • 424
  • 663
another grammar fix
Source Link
David
  • 203
  • 3
  • 7

What would be some really good reasons to not use the SQL_Latin1_General_CI_AS collation on a system which handles English, German, Japanese, and Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from SQL_Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently thatthan Japanese_CI_AS and SQL_Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, and SAP use?)
  4. Does SQL_Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in SQL_Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

What would be some really good reasons to not use the SQL_Latin1_General_CI_AS collation on a system which handles English, German, Japanese, Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from SQL_Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently that Japanese_CI_AS and SQL_Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, SAP use?)
  4. Does SQL_Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in SQL_Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

What would be some really good reasons to not use the SQL_Latin1_General_CI_AS collation on a system which handles English, German, Japanese, and Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from SQL_Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently than Japanese_CI_AS and SQL_Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, and SAP use?)
  4. Does SQL_Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in SQL_Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

Added tag to specify that I'm using Microsoft SQL Server 2008 R2, and also corrected collation names (again)
Source Link
David
  • 203
  • 3
  • 7

Why not use Latin1_General_CI_ASSQL_Latin1_General_CI_AS for a global system?

What would be some really good reasons to not use the Latin1_General_CI_ASSQL_Latin1_General_CI_AS collation on a system which handles English, German, Japanese, Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from Latin1_General_CI_ASSQL_Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently that Japanese_CI_AS and Latin1_General_CI_ASSQL_Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, SAP use?)
  4. Does Latin1_General_CI_ASSQL_Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in Latin1_General_CI_ASSQL_Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

Why not use Latin1_General_CI_AS for a global system?

What would be some really good reasons to not use the Latin1_General_CI_AS collation on a system which handles English, German, Japanese, Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently that Japanese_CI_AS and Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, SAP use?)
  4. Does Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

Why not use SQL_Latin1_General_CI_AS for a global system?

What would be some really good reasons to not use the SQL_Latin1_General_CI_AS collation on a system which handles English, German, Japanese, Chinese data?

I'm having a really hard time finding good sources which compare collations and answer my above question as well as the following

  1. How is Japanese_CI_AS different from SQL_Latin1_General_CI_AS when it comes to sorting non-Japanese characters?
  2. Does UCA sort differently that Japanese_CI_AS and SQL_Latin1_General_CI_AS?
  3. What is standard industry practice for systems used globally? (For example, what does Facebook, Twitter, Google, Flickr, Baidu or Microsoft, IBM, SAP use?)
  4. Does SQL_Latin1_General_CI_AS define a sort order for Japanese characters? If not, how/why does Japanese text work in SQL_Latin1_General_CI_AS?

Basically I'm trying to learn how to pick the appropriate collation :)

Thanks in advance!

I got the collation name wrong, so I fixed it.
Source Link
David
  • 203
  • 3
  • 7
Loading
added a question I forgot to write
Source Link
David
  • 203
  • 3
  • 7
Loading
Source Link
David
  • 203
  • 3
  • 7
Loading