216 UPDATE_SQL= Data Set Option Chapter 10
YES
specifies that Teradata waits to acquire the lock, so SAS/ACCESS waits indefinitely
until it can acquire the lock.
NO
specifies that Teradata fails the lock request if the specified DBMS resource is locked.
Details
If you specify UPDATE_MODE_WAIT=NO and if a different user holds a restrictive
lock, then your SAS step fails and SAS/ACCESS continues the job by processing the
next step. If you specify UPDATE_MODE_WAIT=YES, SAS/ACCESS waits indefinitely
until it can acquire the lock.
A restrictive lock means that a different user is holding a lock that prevents you from
obtaining your desired lock. Until the other user releases the restrictive lock, you
cannot obtain your lock. For example, another user’s table-level WRITE lock prevents
you from obtaining a READ lock on the table.
Use SAS/ACCESS locking options only when Teradata’s standard locking is
undesirable.
For more information, see the documentation for the interface to Teradata.
See Also
To assign this option to a group of relational DBMS tables or views, see the
LIBNAME option “UPDATE_MODE_WAIT= LIBNAME Option” on page 131.
UPDATE_SQL= Data Set Option
Determines the method that is used to update and delete rows in a data source
Valid in:
DATA and PROC steps (when accessing DBMS data using SAS/ACCESS
software)
DBMS support:
ODBC, Microsoft SQL Server
Default value: LIBNAME setting
Syntax
UPDATE_SQL=YES | NO
Syntax Description
YES
specifies that SAS/ACCESS uses Current-of-Cursor SQL to update or delete rows in
a table.
NO
specifies that SAS/ACCESS uses the SQLSetPos() API to update or delete rows in a
table.
