170 DBCOMMIT= Data Set Option Chapter 10
CURSOR_TYPE= OLE DB Properties Applied
DYNAMIC
DBPROP_OTHERINSERT=TRUE,
DBPROP_OTHERUPDATEDELETE=TRUE
KEYSET_DRIVEN
DBPROP_OTHERINSERT=FALSE,
DBPROP_OTHERUPDATEDELET=TRUE
STATIC
DBPROP_OTHERINSERT=FALSE,
DBPROP_OTHERUPDATEDELETE=FALSE
See Also
To assign this option to a group of relational DBMS tables or views, see the
LIBNAME option “CURSOR_TYPE= LIBNAME Option” on page 82.
DBCOMMIT= Data Set Option
Causes an automatic COMMIT (a permanent writing of data to the DBMS) after a specified number
of rows have been processed
Valid in:
DATA and PROC steps (when accessing DBMS data using SAS/ACCESS
software)
DBMS support: DB2 OS/390, DB2 UNIX/PC, Informix, ODBC, OLE DB, Oracle, Microsoft
SQL Server, SYBASE, Teradata
Default value: the current LIBNAME setting
Syntax
DBCOMMIT=n
Syntax Description
n
is an integer greater than or equal to 0.
Details
DBCOMMIT= affects update, delete, and insert processing. The number of rows
processed includes rows that are not processed successfully. When DBCOMMIT=0, a
commit is issued only once (after the procedure or DATA step completes).
If the DBCOMMIT= option is explicitly set, SAS/ACCESS fails any update that has a
WHERE clause.
Note: If you specify both DBCOMMIT= and ERRLIMIT= , and these options collide
during processing, then the COMMIT is issued first and the ROLLBACK is issued
second. Because the COMMIT (caused by the DBCOMMIT option) is issued prior to the
ROLLBACK (caused by the ERRLIMIT= option), the DBCOMMIT= option is said to
override the ERRLIMIT= option in this situation.
