Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There are compilation issues in our TFS builds since some non-English characters are not recognized. Could this be caused by SQL Server collation? Its been installed as SQL_Latin1_General_CP1_CI_AS (not locale-specific).

Update: Thanks to both answers for leading me to the right direction. This article also may help other people with the same problem.

share|improve this question
up vote 1 down vote accepted

As db2 stated collation controls sort order not what characters can fit into the column. As long as the columns are uni-code they will store any value that a computer can generate.

In addition to controlling sort order they also control accent sensitivity for sorting as well as case sensitivity. In you case the columns are case insensitive and accent sensitive which I would assume are the correct collations for TFS as I believe that it creates the databases for you when you install it for the first time.

share|improve this answer

I can't say with 100% certainty (there could be some obscure little details of TFS that I'm not familiar with), but I very much doubt it. The collation controls things like sort order, and string equality, and only at the database tier. Any application working with character columns is going to get the same data out of them that it originally put in, regardless of collation.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.