SQL Server Language Not Supported

Question

Hello,

Data in Bashkir (Russia) language is transferred but appears as a question mark. What needs to be done to support SQL Server language

Up: Bashkir (Russia)

Down : Normally Russia

Answer 1

To store Cyrillic data in Bashkir, you need to use nvarchar, or you if use varchar, you need a collation with code page 1251 or 65001 (UTF-8.)

Since you have a Russian word in the second row, it appears that your table column is all geared for Cyrillic. OK, Russian is not Bashkir, but the character repertoires are not that far apart are they? So rather something has gone wrong on input. Since I don't know how the data made it to the database, I can't say what went wrong. But a common error is to leave out the N when you use nvarchar and a collation for a different code page than your own language.

This illustrates:

CREATE DATABASE Latin COLLATE Latin1_General_100_CI_AS
go
USE Latin
go
SELECT 'Привет', N'Привет'
go
CREATE DATABASE Cyrillic COLLATE Bashkir_100_CI_AS
go
USE Cyrillic
go
SELECT 'Привет', N'Привет'
go
USE tempdb
go
DROP DATABASE Latin
DROP DATABASE Cyrillic

To check your database collation run

SELECT databasepropertyex(db_name(), 'Collation')

To check the collation for your columns, use sp_help.

Answer 2

Hi @Rabia Kurnaz

In Object Explorer, right-click the database that you want and click Properties.

Click the Options page and select a collation from the Collation drop-down list.

Refer to this doc for more details: Set or change the database collation.

Best regards,

Cosmog Hong

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.