UPDATE_ISOLATION_LEVEL= LIBNAME Statement Option

Specifies the degree of isolation of the current application process from other concurrently running application processes.

Valid in:	SAS/ACCESS LIBNAME statement
Category:	Data Set Control
Alias:	UIL= [Greenplum, HAWQ, SAP IQ]
Default:	DBMS-specific
Restriction:	DB2 under UNIX and PC Hosts, Greenplum, HAWQ, ODBC: If you do not specify UPDATE_LOCK_TYPE=ROW for these interfaces, this option is ignored.
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 IQ, Teradata, Vertica, Yellowbrick
Notes:	This option is ignored in the interfaces to DB2 under UNIX and PC Hosts and ODBC if you do not specify UPDATE_LOCK_TYPE=ROW.
Notes:	Support for Yellowbrick was added in SAS 9.4M7.
See:	CONNECTION= LIBNAME option, 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= data set option, UPDATE_LOCK_TYPE= LIBNAME option, UPDATE_LOCK_TYPE= data set option

Table of Contents

Syntax

UPDATE_ISOLATION_LEVEL=DBMS-specific-value

The degree of isolation specifies the degree to which these items are affected:

Rows that the current application reads and updates are available to other concurrently executing applications.
Update activity of other concurrently executing application processes can affect the current application.

For more information, including a list of supported values, see the information about locking for your interface:

Last updated: February 3, 2026