Turkish character problem in SQL Server 2000

From: Aynur Demircan (Demircan_at_discussions.microsoft.com)
Date: 10/15/04


Date: Fri, 15 Oct 2004 00:35:04 -0700

Hi,
I'm trying to migrate a Sybase SQL Anywhere database to SQL server 2000. I
have a problem when I choose "Turkish_CI_AS" as the database collation: The
problem occurs when I query a table with a column named "CompID".
When I write "Select compid from Table1", SQL Server returns the error
"Column compid not found".
I get from that error that there's a mismatch between uppercase I and
lowercase I(which I use as i).
When I use lowercase I(not i) there's no error.
But my problem is, we have lots of programs written for querying the
database tables
which frequently use lowercase i instead of I.
When I change the collation to Latin1_General_CI_AS, the problem is solved
but then there comes a different problem:
This time, colums with type char(x) don't display the Turkish characters in
the rows correctly. (characters like 'Ç','Ş', 'ş''İ'(dotted uppercase I),'ü')
. To solve this problem, I change the collation of the column with the char
data type to Turkish_CI_AS but still the problem is not solved. (I think my
regional settings and default language settings are correct(Turkish).
 

I'll be really glad if someone can help me about the problem.
Thanks,

Aynur
     



Relevant Pages

  • Re: Database collation error after moving to a remote sql server
    ... > I've recently my SMS 2003 database to a remote sql server (it was ... > Server]Cannot resolve collation conflict for equal to operation. ... The char, varchar, text, nchar, nvarchar, or ntext system data types, ...
    (microsoft.public.sms.setup)
  • Re: Different collations in a database
    ... The SQL Server itself is correctly setup to use Finnish_Swedish_CI_AS, ... the fields back to database default. ... database with the correct collation. ... Books Online for SQL Server 2005 at ...
    (comp.databases.ms-sqlserver)
  • RE: Advice on Create a SQL Server
    ... Use the default collation. ... Mode" - it depends on how you will be connecting to your database. ... domain, and running on a windows domain account, it is better to run under ... to SQL Server using a username/password. ...
    (microsoft.public.sqlserver.setup)
  • Collation of Database and Server
    ... I am working a problem according to the collation of MS SQL Server ... 2000 and a database. ... Environment: German MS SQL Server 2000 SP3a ...
    (microsoft.public.de.sqlserver)
  • Collation of Database and Server
    ... I am working a problem according to the collation of MS SQL Server ... 2000 and a database. ... Environment: German MS SQL Server 2000 SP3a ...
    (microsoft.public.sqlserver.server)