
The LIBNAME Statement for Relational Databases INSERTBUFF= LIBNAME Option 103
alternate method (used when this option is set to NO) uses the OLE DB
IRowsetChange interface.
Microsoft SQL Server Details: The Microsoft SQL Server default is YES. When
INSERT_SQL=NO, the SQLSetPos (SQL_ADD) function inserts rows in groups that are
the size of the INSERTBUFF= option value. The SQLSetPos (SQL_ADD) function does
not work unless it is supported by your driver.
See Also
To apply this option to an individual data set, see the data set option “INSERT_SQL=
Data Set Option” on page 193.
INSERTBUFF= LIBNAME Option
Specifies the number of rows in a single insert operation
Valid in:
the SAS/ACCESS LIBNAME statement
DBMS support: DB2 UNIX/PC, ODBC, OLE DB, Oracle, Microsoft SQL Server
Default value:
DBMS-specific
Syntax
INSERTBUFF=positive-integer
Syntax Description
positive-integer
specifies the number of rows to insert. SAS allows the maximum that is allowed by
the DBMS.
Details
The optimal value for this option varies with factors such as network type and available
memory. You may need to experiment with different values in order to determine the
best value for your site.
The SAS application messages that indicate the success or failure of an insert
operation only represent information for a single insert, even when multiple inserts are
performed. Therefore, when you assign a value that is greater than INSERTBUFF=1,
these messages may be incorrect.
If you specify the DBCOMMIT= option with a value that is less than the value of
INSERTBUFF=, then DBCOMMIT= overrides INSERTBUFF=.
Note: When you insert by using the VIEWTABLE window or the FSVIEW or
FSEDIT procedure, use INSERTBUFF=1 to prevent the DBMS interface from trying to
insert multiple rows. These features do not support inserting more than one row at a
time.
Note: Additional driver-specific restrictions might apply.