13.07.2015 Views

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

118 DB_LENGTH_SEMANTICS_BYTE= LIBNAME Option 4 Chapter 10DB_LENGTH_SEMANTICS_BYTE= LIBNAME OptionIndicates whether CHAR/VARCHAR2 column lengths are specified in bytes or characters whencreating an Oracle table.Default value: YESValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: OracleSyntaxDB_LENGTH_SEMANTICS_BYTE=YES | NOSyntax DescriptionYESspecifies that CHAR and VARCHAR2 column lengths are specified in characterswhen creating an Oracle table. The byte length is derived by multiplying the numberof characters in <strong>SAS</strong> with DBSERVER_MAX_BYTES= value.NOspecifies that CHAR and VARCHAR2 column lengths are specified in bytes whencreating an Oracle table. The CHAR keyword is also added next to the length valueto indicate that this is the character, not byte, length. For fixed-width encoding, thenumber of characters is derived by dividing the byte length in <strong>SAS</strong> <strong>for</strong> the variableby the value in DBCLIENT_MAX_BYTES=. For variable-width encoding, thenumber of characters remains the same as the number of bytes.DetailsThis option is appropriate only when creating Oracle tables from <strong>SAS</strong>. It is there<strong>for</strong>eignored in other contexts, such as reading or updating tables.Length values chosen <strong>for</strong> variable-width encodings might be more than what isactually needed.See Also“DBSERVER_MAX_BYTES= LIBNAME Option” on page 136

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!