UPDATE_ISOLATION_LEVEL= Data Set Option

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

Valid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software)
Category: Data Set Control
Alias: UIL= [Greenplum, HAWQ, Microsoft SQL Server, SAP IQ]
Default: LIBNAME option value
Data source: Amazon Redshift, DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HAWQ, Microsoft SQL Server, MySQL, ODBC, OLE DB, Oracle, PostgreSQL, SAP ASE, 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.
See: READ_ISOLATION_LEVEL= LIBNAME option, READ_LOCK_TYPE= LIBNAME option, READ_LOCK_TYPE= data set option, UPDATE_ISOLATION_LEVEL= LIBNAME option, UPDATE_LOCK_TYPE= LIBNAME option, UPDATE_LOCK_TYPE= data set option, and DBMS-specific locking information in the reference section for your SAS/ACCESS interface

Table of Contents

Syntax

UPDATE_ISOLATION_LEVEL=DBMS-specific-value

Details

The degree of isolation indicates 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.
Last updated: February 3, 2026