The LIBNAME Statement for Relational Databases

ADJUST_NCHAR_COLUMN_LENGTHS= LIBNAME Option

Specifies whether to adjust the lengths of CHAR or VARCHAR data type columns.

Default value:	YES
Valid in:	SAS/ACCESS LIBNAME statement
DBMS support:	Oracle

Syntax
Syntax Description
Examples
See Also

Syntax

ADJUST_NCHAR_COLUMN_LENGTHS=YES | NO

Syntax Description

YES: indicates that column lengths are multiplied by the DBSERVER_MAX_BYTES= value.
NO: indicates that column lengths that NCHAR or NVARCHAR columns specify are multiplied by the maximum number of bytes per character value of the national character set for the database.

Examples

NCHAR column lengths are no longer adjusted to client encoding when ADJUST_NCHAR_COLUMN_LENGTHS=NO, as shown in this example.

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