Brothers who have research on the garbled problem come in

kolerk

The cause of the problem is:

My website system has such a function:
To query user information by querying the user account.
When the user name is English, there is no problem, but when the user name is Chinese, no information can be found.
So I did some work and found some problems.

(1) I checked the pull stored procedure and verified it directly with the Chinese name in the database. No problem.
The executed statement is as follows
． ． ． ． ．
exec process name, @username process parameter = N'user name '-N stands for unicode encoding
． ． ． ． ．
(2) So I opened sql server profiler to monitor. Then I visited the webpage and found the calling statement shown below:
． ． ． ． ．
exec procedure name, @username procedure parameter = '? ? ? '-The difference from the above is that one N is missing, resulting in garbled characters.
． ． ． ． ．
(3) The key to solving the problem now is how to enable the database to execute the statement in (1) when the query comes directly from the website.

kolerk

The website system coding uses UTF-8, and tests show that there is no garbled code before transmission to the database process, everything is normal.

fanfan1980

Multilingual version is best to use unicode type

shenmue024

exec process name, @username process parameter = N'user name '
// Is this sentence written directly in sql or in the form of parameter addition?

kolerk

Describe again:
(1) I checked the pull stored procedure, and executed the procedure in the database. Input Chinese name parameters to verify that there were no problems.
The resulting execution statement is as follows
． ． ． ． ．
exec process name, @username process parameter = N'user name '-N stands for unicode encoding
． ． ． ． ．
(2) So I opened sql server profiler to monitor. Then I visited the webpage and found that the calling statement displayed by sql server profiler was as follows:
． ． ． ． ．
exec procedure name, @username procedure parameter = '? ? ? '-The difference from the above is that one N is missing, resulting in garbled characters.
． ． ． ． ．
(3) The key to solving the problem now is how to enable the database to execute the statement in (1) when completing the query from the website.

kolerk

Describe again:
(1) I checked the pull stored procedure, and executed the procedure in the database. Input Chinese name parameters to verify that there were no problems.
The resulting execution statement is as follows
． ． ． ． ．
exec process name, @username process parameter = N'user name '-N stands for unicode encoding
． ． ． ． ．
(2) So I opened sql server profiler to monitor. Then I visited the webpage and found that the calling statement displayed by sql server profiler was as follows:
． ． ． ． ．
exec procedure name, @username procedure parameter = '? ? ? '-The difference from the above is that one N is missing, resulting in garbled characters.
． ． ． ． ．
(3) The key to solving the problem now is how to enable the database to execute the statement in (1) when completing the query from the website.

shenmue024

Directly with command.Text = "exec process N'name '"

Don't @ parameter =

everever30

If you pass parameters, the parameter type is nvarchar. If you use SQL string concatenation, refer to the above.

crabhero

If the database uses unicode storage, the parameter value must also use utf-8, which can be used before querying
encoding.getstring () for conversion

shihai

First determine if you have to use unicode, it seems that the demand is not too much. Sure, but maybe you do n’t need it at all