The LIBNAME Statement for Relational Databases

DBCLIENT_MAX_BYTES= LIBNAME Option

Specifies the maximum number of bytes per single character in the database client encoding, which matches SAS encoding.

Default value:	always set to match the maximum bytes per single character of SAS session encoding (see "Details")
Valid in:	SAS/ACCESS LIBNAME statement
DBMS support:	Oracle

Syntax
Details
Examples
See Also

Syntax

DBCLIENT_MAX_BYTES=max-client-bytes

Details

Use this option as the multiplying factor to adjust column lengths for CHAR and NCHAR columns for client encoding. In most cases, you need not set this option because the default is sufficient.

Examples

This example uses default values for all options.

libname x1 &engine &connopt
proc contents data=x1.char_sem; run;
proc contents data=x1.nchar_sem; run;
proc contents data=x1.byte_sem; run;
proc contents data=x1.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;