Question

8
Replies
844
Views
 Binod Garg (BinodG81)
Infosys

Infosys
AU
BinodG81 Member since 2014 36 posts
Infosys
Posted: November 7, 2016
Last activity: March 21, 2017
Posted: 7 Nov 2016 2:44 EST
Last activity: 21 Mar 2017 20:44 EDT
Closed

Saving Japanese characters in SQL Server database

We have an application where we are saving the user data entered in japanese characters to the SQL Server database. However we observed that the data stored is the db appears as '????' . The type of the column is varchar . Is this an expected behaviour? Any quick changes to the db that could help resolve this issue?

***Updated by moderator: Lochan to add Categories***

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 6 Jan 2017 1:49 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Technical Lead
Pegasystems Inc.
IN

HI Binod,


Try updating column to nvarchar from varchar.


Once this is done values while inserting or updating should be prefixed with N


eg Update tableX set y = N'JapaneseCharacter' where condition.


Above will help you verify if DB is accepting Japanese character.


Raise an SR in case not done yet.


 


Thanks,


Ujjwal


 


 
Posted: 4 years ago
Posted: 6 Jan 2017 3:33 EST
Sudhish Othoyoth Puthiyapurayil (othos)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Binod,


The same issue is reported by lot of user's in stackoverflow. Kindly refer the below links correct answer marked and perform the same to recitify this issue.


http://stackoverflow.com/questions/4600721/japanese-characters-storing-as-question-mark-in-sql-server-db


http://stackoverflow.com/questions/761036/why-is-sql-server-storing-question-mark-characters-instead-of-japanese-character


Regards,


Sudhish OP
Posted: 4 years ago
Posted: 27 Feb 2017 20:09 EST
Jun Hasegawa (hasej)
PEGA
Lead System Architect
Pegasystems Inc.
JP

Hi Binod, 


I am facing the same issue. Do you have a resolution on your side? 


Thanks, 


Jun
Posted: 4 years ago
Posted: 28 Feb 2017 7:58 EST
Shanthini Charles (Shanthini_Charles)
PEGA
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Jun,


As stated above have you modified to nvarchar from varchar and also when doing your insert or update, are you prefixing your value with N at the front?


Regards,


Shanthini Charles
Posted: 4 years ago
Posted: 2 Mar 2017 2:02 EST
Jun Hasegawa (hasej)
PEGA
Lead System Architect
Pegasystems Inc.
JP

Hi Shanthini, 


Thank you for your response. 


I am seeing the same issue at the OOTB table columns like pr_operators.pyPosition, so I could modified to nvarchar but cannot put prefix "N" when saving it. I am not sure it is good idea to modify OOTB table column. 


 


Regards, 


Jun