Specifies how data in a DBMS table is locked during an update transaction.
| Valid in: | DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software) |
|---|---|
| Category: | Data Access |
| Default: | LIBNAME option value |
| Data source: | Amazon Redshift, DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HAWQ, Microsoft SQL Server, ODBC, OLE DB, Oracle, PostgreSQL, SAP ASE, SAP HANA, SAP IQ, Teradata, Vertica, Yellowbrick |
| Notes: | Support for Amazon Redshift was added in the April 2016 release of SAS/ACCESS. |
| Support for Yellowbrick was added in SAS 9.4M7. | |
| Tip: | If you omit UPDATE_LOCK_TYPE=, you receive either the default action for the DBMS that you are using, or a lock for the DBMS that was specified with the LIBNAME statement. You can specify a lock for one DBMS table by using the data set option or for a group of DBMS tables by using the LIBNAME option. |
| See: | READ_ISOLATION_LEVEL= LIBNAME option, READ_ISOLATION_LEVEL= data set option, READ_LOCK_TYPE= LIBNAME option, READ_LOCK_TYPE= data set option, UPDATE_ISOLATION_LEVEL= LIBNAME option, UPDATE_ISOLATION_LEVEL= data set option, UPDATE_LOCK_TYPE= LIBNAME option, and DBMS-specific locking information in the reference section for your SAS/ACCESS interface |
Table of Contents
locks a row if any of its columns are to be updated.
| Data source | Amazon Redshift, DB2 under UNIX and PC Hosts, Greenplum, HAWQ, Microsoft SQL Server, ODBC, OLE DB, Oracle, PostgreSQL, SAP HANA, Vertica |
|---|
locks a page of data. The number of bytes in a page is specific to the DBMS.
| Data source | SAP ASE |
|---|
locks the entire DBMS table.
| Data source | DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HAWQ, Microsoft SQL Server, ODBC, Oracle, SAP HANA, Teradata |
|---|
does not lock the DBMS table, page, or any rows when reading them for update.
| Data source | Amazon Redshift, Microsoft SQL Server, ODBC, Oracle, PostgreSQL, SAP ASE, SAP HANA |
|---|
locks the entire DBMS view.
| Data source | Teradata |
|---|