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.

The LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 USE_ODBC_CL= LIBNAME Option 199See AlsoTo apply this option to an individual data set, see the “UPDATE_SQL= Data SetOption” on page 398.“INSERT_SQL= LIBNAME Option” on page 151UPDATEBUFF= LIBNAME OptionSpecifies the number of rows that are processed in a single DBMS update or delete operation.Default value: 1Valid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: OracleSyntaxUPDATEBUFF=positive-integerSyntax Descriptionpositive-integeris the number of rows in an operation. <strong>SAS</strong> allows the maximum that the DBMSallows.DetailsWhen updating with the VIEWTABLE window or the FSVIEW procedure, useUPDATEBUFF=1 to prevent the DBMS interface from trying to update multiple rows.By default, these features update only observation at a time (since by default they userecord-level locking, they lock only the observation that is currently being edited).See AlsoTo apply this option to an individual data set, see the “UPDATEBUFF= Data SetOption” on page 399.USE_ODBC_CL= LIBNAME OptionIndicates whether the Driver Manager uses the ODBC Cursor Library.Default value: NOValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statement and some DBMS-specific connectionoptions. See the DBMS-specific reference section <strong>for</strong> details.DBMS support: Aster nCluster, HP Neoview, Microsoft SQL Server, Netezza, ODBC

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

Saved successfully!

Ooh no, something went wrong!