Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
for Unicode support you have to use :
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