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

152 INSERTBUFF= LIBNAME Option 4 Chapter 10NOspecifies that SAS/ACCESS uses an alternate (DBMS-specific) method to insert newrows into a table.DetailsFlat file databases (such as dBASE, FoxPro, and text files) generally have improvedinsert performance when INSERT_SQL=NO. Other databases might have inferiorinsert performance (or might fail) with this setting, so you should experiment todetermine the optimal setting for your situation.HP Neoview: The default is YES.Microsoft SQL Server: The Microsoft SQL Server default is YES. WhenINSERT_SQL=NO, the SQLSetPos (SQL_ADD) function inserts rows in groups that arethe size of the INSERTBUFF= option value. The SQLSetPos (SQL_ADD) function doesnot work unless it is supported by your driver.Netezza: The default is YES.ODBC: The default is YES, except for Microsoft Access, which has a default of NO.When INSERT_SQL=NO, the SQLSetPos (SQL_ADD) function inserts rows in groupsthat are the size of the INSERTBUFF= option value. The SQLSetPos (SQL_ADD)function does not work unless your driver supports it.OLE DB: By default, the OLE DB interface attempts to use the most efficient rowinsertion method for each data source. You can use the INSERT_SQL option to overridethe default in the event that it is not optimal for your situation. The OLE DB alternatemethod (used when this option is set to NO) uses the OLE DB IRowsetChange interface.See AlsoTo apply this option to an individual data set, see the “INSERT_SQL= Data SetOption” on page 330.“INSERTBUFF= LIBNAME Option” on page 152“DBCOMMIT= Data Set Option” on page 297INSERTBUFF= LIBNAME OptionSpecifies the number of rows in a single DBMS insert.Default value: DBMS-specificValid in: SAS/ACCESS LIBNAME statementDBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, Greenplum, HPNeoview, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle, Sybase IQSyntaxINSERTBUFF=positive-integerSyntax Descriptionpositive-integerspecifies the number of rows to insert.