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

Data Set Options for Relational Databases 4 OR_UPD_NOWHERE= Data Set Option 355All rows in the P4 partition are deleted in this example.proc sql;delete from x.orparttest ( or_partition=p4 );quit;In this next example, rows are added to the P4 partition in the table.data new;do i=31 to 39; num=i; output;end;run;proc append base= x.orparttest ( or_partition=p4 );data= new;run;The next example also adds rows to the P4 partition but uses the SQL*Loaderinstead.proc append base= x.orparttest ( or_partition=p4 bulkload=yes );data= new;run;OR_UPD_NOWHERE= Data Set OptionSpecifies whether SAS uses an extra WHERE clause when updating rows with no locking.Alias: ORACLE_73_OR_ABOVE=Default value: LIBNAME settingValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: OracleSyntaxOR_UPD_NOWHERE=YES | NOSyntax DescriptionYESSAS does not use an additional WHERE clause to determine whether each row haschanged since it was read. Instead, SAS uses the SERIALIZABLE isolation level(available with Oracle 7.3 and later) for update locking. If a row changes after theserializable transaction starts, the update on that row fails.NOSAS uses an additional WHERE clause to determine whether each row has changedsince it was read. If a row has changed since being read, the update fails.DetailsUse this option when you are updating rows without locking(UPDATE_LOCK_TYPE=NOLOCK).