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

298 DBCONDITION= Data Set Option 4 Chapter 11DetailsDBCOMMIT= affects update, delete, and insert processing. The number of rowsprocessed includes rows that are not processed successfully. When DBCOMMIT=0,COMMIT is issued only once—after the procedure or DATA step completes.If you explicitly set the DBCOMMIT= option, SAS/ACCESS fails any update with aWHERE clause.If you specify both DBCOMMIT= and ERRLIMIT= and these options collide duringprocessing, COMMIT is issued first and ROLLBACK is issued second. BecauseCOMMIT is issued (through the DBCOMMIT= option) before ROLLBACK (through theERRLIMIT= option), DBCOMMIT= overrides ERRLIMIT=.DB2 Under UNIX and PC Hosts: When BULKLOAD=YES, the default is 10000.Teradata: For the default behavior of this option, see FastLoad description in theTeradata section. DBCOMMIT= and ERRLIMIT= are disabled for MultiLoad to preventany conflict with ML_CHECKPOINT=.ExampleA commit is issued after every 10 rows are processed in this example:data oracle.dept(dbcommit=10);set myoralib.staff;run;See AlsoTo assign this option to a group of relational DBMS tables or views, see the“DBCOMMIT= LIBNAME Option” on page 120.“BULKLOAD= LIBNAME Option” on page 102“BULKLOAD= Data Set Option” on page 290“ERRLIMIT= LIBNAME Option” on page 146“ERRLIMIT= Data Set Option” on page 325“INSERT_SQL= LIBNAME Option” on page 151“INSERT_SQL= Data Set Option” on page 330“INSERTBUFF= LIBNAME Option” on page 152“INSERTBUFF= Data Set Option” on page 331“ML_CHECKPOINT= Data Set Option” on page 336“Using FastLoad” on page 804DBCONDITION= Data Set OptionSpecifies criteria for subsetting and ordering DBMS data.Default value:noneValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, Informix, Microsoft SQL Server, MySQL, Netezza, ODBC,OLE DB, Oracle, Sybase, Sybase IQ, Teradata