0

I currently store my string fields in SQL Server as varchar(x). The Database stores records from across the globe, but non standard characters, such as 'glyphics from Asia or Cyrillic Script/Azbuka from Russia appear as '?????????????' question marks.

How can I prevent this from happening and what are the ramifications of changing SQL Server to handle such input.

aSystemOverload
  • 2,994
  • 18
  • 49
  • 73

1 Answers1

1

for Unicode support you have to use :

nvarchar(x)

nchar and nvarchar (Transact-SQL)

nchar [ ( n ) ] - Fixed-length Unicode character data of n characters. n must be a value from 1 through 4,000.

nvarchar [ ( n | max ) ] - Variable-length Unicode character data. ncan be a value from 1 through 4,000.

Also, you can refer:

What is the difference between varchar and nvarchar?

varchar vs nvarchar performance

Community
  • 1
  • 1
Kapil Khandelwal
  • 15,958
  • 2
  • 45
  • 52