|
Problem(Abstract) |
This property determines if string parameters are sent to
Microsoft SQL Server using Unicode or default encoding. If set to true,
string parameters are sent to Microsoft SQL Server in Unicode. If set to
false, string parameters are sent using the default encoding. |
|
|
|
Cause |
Considerations for deciding whether to set the
SendStringParametersAsUnicode to true or false. |
|
|
Resolving the
problem |
Setting the SendStringParametersAsUnicode property
of the WebSphere® embedded ConnectJDBC driver for MS SQL Server to true or
false determines whether string parameters are sent to the Microsoft SQL
Server database in Unicode or in the default character encoding of the
database. If set to true, string parameters are sent in Unicode. If set to
false, string parameters are sent in the default encoding, which can
improve performance because the server does not need to convert Unicode
characters to the default encoding.
Use default encoding only if the parameter string data you specify is the
same as the default encoding of the database. The default value for this
parameter is true. If a value is specified for the CodePageOverride
property and this property is set to true, this property is ignored and a
warning is generated.
Setting SendStringParametersAsUnicode to false can result in data
corruption if the server-side character encoding uses high order bits; for
example, SQL Server data types, the N types are Nchar, Ntext, and
Nvarchar. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|