The LIBNAME Statement for Relational Databases |
Default value: | conditional (see "Syntax Description") |
Valid in: | SAS/ACCESS LIBNAME statement |
DBMS support: | Oracle |
Syntax | |
Syntax Description | |
Examples | |
See Also |
Syntax |
ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES | NO |
indicates that column lengths are divided by the DBSERVER_MAX_BYTES= value and then multiplied with the DBCLIENT_MAX_BYTES= value. So if DBCLIENT_MAX_BYTES is greater than 1, then ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES.
indicates that any column lengths that byte semantics specify on the server are used as is on the client. So if DBCLIENT_MAX_BYTES=1, then ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO.
Examples |
When ADJUST_BYTE_SEMANTICS_COLUMN_LENGTHS=YES, column lengths that byte semantics creates are adjusted with client encoding, as shown in this example.
libname x3 &engine &connopt ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES; proc contents data=x3.char_sem; run; proc contents data=x3.nchar_sem; run; proc contents data=x3.byte_sem; run; proc contents data=x3.mixed_sem; run;
In this example, various options have different settings.
libname x5 &engine &connopt ADJUST_NCHAR_COLUMN_LENGTHS=NO ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO DBCLIENT_MAX_BYTES=3; proc contents data=x5.char_sem; run; proc contents data=x5.nchar_sem; run; proc contents data=x5.byte_sem; run; proc contents data=x5.mixed_sem; run;
This example also uses different settings for the various options.
libname x6 &engine &connopt ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES ADJUST_NCHAR_COLUMN_LENGTHS=YES DBCLIENT_MAX_BYTES=3; proc contents data=x6.char_sem; run; proc contents data=x6.nchar_sem; run; proc contents data=x6.byte_sem; run; proc contents data=x6.mixed_sem; run;
See Also |
ADJUST_NCHAR_COLUMN_LENGTHS= LIBNAME Option
DBCLIENT_MAX_BYTES= LIBNAME Option
DBSERVER_MAX_BYTES= LIBNAME Option
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.