ODBC Server Reference Manual

Transact-SQL Language
HP NonStop ODBC Server Reference Manual—429151-002
4-34
NULL Values
.
When used with the NonStop ODBC Server, the % wild-card character works
differently than it does in Transact-SQL:
•
In the NonStop ODBC Server, character comparisons are case sensitive. In
Transact-SQL, however, character comparisons are not case sensitive.
For example, the following comparison would locate the string “San Francisco” if
done with Transact-SQL, but not if done with the NonStop ODBC Server:
%san%
•
Because NonStop SQL/MP recognizes trailing blanks as part of a string, you must
place the % wild-card character at the end of a comparison; this is not necessary in
Transact-SQL.
For example, when searching a 12-character field containing “ABC”, Transact-SQL
sees the value as “ABC” and NonStop SQL/MP sees it as “ABC ” (with nine
trailing blanks). Consequently, when searching for the string using the NonStop
ODBC Server, you must use the following comparison:
%ABC%
For more information, see the following documents:
NULL Values
The only difference between NULL values in Transact-SQL and NULL values in the
NonStop ODBC Server is the order in which data is displayed.
Table 4-13 summarizes how NULL values affect the order in which data is displayed in
Transact-SQL and in statements executed using the NonStop ODBC Server.
Table 4-12. NonStop ODBC Server Support of Wild-Card Characters
Transact-SQL
Wild-Card Character NonStop ODBC Server Support
%x
_x
[ character-range ]–
[ character-set ]–
[ ^character-range ]–
[ ^character-set ]–
x Indicates a supported wild-card character
– Indicates an unsupported wild-card character
For Information On See
Wild-card characters in Transact-SQL Microsoft SQL Server Transact-SQL Reference
Wild-card characters in NonStop SQL/MP NonStop SQL/MP Reference Manual