Does SQL_Latin1_General_CP1_CI_AS supports Cyrillic characters with unicode data-types?

  • Hi All,

    I have an consolidated SQL Server environment. And it includes many databases with different collations. My instance collation is SQL_Latin1_General_CP1_CI_AS.

    But today, when i would create a database Kazakh_100_CI_AS with cyrillic characters. I could not save data in varchar datatypes. Just i changed all datatypes to nvarchar, an it was succeeded.

    Are there a codepage restriction with SQL_Latin1_General_CP1_CI_AS with Kazakh_100_CI_AS ?

    How do i achive to store data with varchar(not nvarchar?) without any change of instance collation?

    Regards,

  • The instance collation is just the default when creating databases. If you explicitly define a collation when creating a database (or tables), the instance default will be ignored.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I did just you told. But i am getting below error:

    "The Collation specified by SQL Server is not supported."

  • What exactly did you do?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • My database collation is different from Instance.

    only while querying table, i got the error. But i successfully import data with ETL.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply