DDBCOMIT= Data Set Option

Specifies the number of rows that are processed before a database COMMIT statement is issued.

Alias: DBCOMMIT=
Default: 0
See: DDBERLMT=

Syntax

DDBCOMIT= n

Syntax Description

n
is an integer that is equal to or greater than zero.

Details

The DDBCOMIT= data set option affects update, delete, and insert processing. The number of rows includes rows that are not processed successfully. DDBCOMIT=0 is the default setting and specifies that a commit is issued only once after the procedure or DATA step completes. In the following example, a commit is issued after every 10 rows are inserted:
proc append data=mylib.staff base=datacom.dept (ddbload=1 ddbcomit=10);
run;
For DDBCOMIT= to be enforced, CA-Datacom/DB logging must be turned on and TXNUNDO=YES must be specified in the User Requirements Table (URT). TXNUNDO=YES is specified in the default URT that is shipped with SAS/ACCESS interface to CA-Datacom/DB software. If DDBCOMIT > 0 and logging is off, then the locks are released, but a commit is not issued.
If DDBCOMIT=0 and DDBERLMT > 1, a rollback is attempted when DDBERLMT=is reached. If DDBCOMIT > 0, a commit can be issued before a rollback that is needed by the DDBERLMT= option. For more information, see DDBERLMT=.
In PROC SQL, the DDBCOMIT= option enables PROC SQL UNDO_POLICY=REQUIRED for both DDBCOMIT=0 and DDBCOMIT > 0.