READ_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:	RIL= [Greenplum, HAWQ, Microsoft SQL Server, SAP IQ]
Default:	COMMITTED READ [Informix]
	CS [DB2 under UNIX and PC Hosts]
	determined by the DBMS [DB2 under z/OS]
	RC [Amazon Redshift, Greenplum, HAWQ, Microsoft SQL Server, ODBC, PostgreSQL, SAP IQ, Vertica, Yellowbrick]
	READCOMMITTED [Oracle]
	1 [SAP ASE]
	none [OLE DB]
	Set the default in the DB2CLI.ini file [ODBC]. For valid values, see your DBMS documentation.
Interaction:	For DB2 under UNIX and PC Hosts and ODBC, this option is ignored if you do not set the READ_LOCK_TYPE= LIBNAME option to ROW.
Data source:	Amazon Redshift, DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HAWQ, Informix, Microsoft SQL Server, ODBC, OLE DB, Oracle, PostgreSQL, SAP ASE, SAP IQ, Teradata, Vertica, Yellowbrick
Note:	Support for Yellowbrick was added in SAS 9.4M7.
See:	CONNECTION= LIBNAME option, READ_ISOLATION_LEVEL= data set option, READ_LOCK_TYPE= LIBNAME option, READ_LOCK_TYPE= data set option, READ_MODE_WAIT= LIBNAME option, UPDATE_ISOLATION_LEVEL= LIBNAME option, UPDATE_ISOLATION_LEVEL= data set 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

READ_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 about the values that are accepted, see your DBMS documentation.

Last updated: February 3, 2026