The LIBNAME Statement for Relational Databases |
Specifies how data in a DBMS table is locked during an
update
transaction.
Default value: |
DBMS-specific
|
Valid in: |
SAS/ACCESS LIBNAME
statement
|
DBMS support: |
DB2 under UNIX and PC Hosts, DB2 under z/OS,
Microsoft SQL Server, ODBC, OLE DB, Oracle, Sybase, Sybase IQ, Teradata
|
UPDATE_LOCK_TYPE=ROW | PAGE | TABLE | NOLOCK |VIEW
|
-
ROW [valid for DB2 under UNIX and PC Hosts, Microsoft
SQL Server, ODBC, Oracle]
-
locks a row if any of its columns are to
be updated.
-
PAGE [valid for Sybase]
-
locks a page of data, which is a DBMS-specific
number of bytes. This value is not valid for the Sybase interface when you
use the .
- TABLE [valid for DB2 under UNIX and PC Hosts, DB2 under z/OS,
Microsoft SQL Server, ODBC, Oracle, Sybase IQ, Teradata]
-
locks the entire DBMS table.
- NOLOCK [valid for Microsoft SQL Server, ODBC with Microsoft SQL Server
driver, OLE DB, Oracle, Sybase]
-
does not lock the DBMS table, page, or any
rows when reading them for update. (This value is valid in the Microsoft SQL
Server, ODBC, Oracle, and Sybase interfaces.)
-
VIEW [valid for Teradata]
-
locks the entire DBMS view.
You can set 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 the locking topic for your interface in the DBMS-specific reference
section for details.
To
apply this option to an individual data set, see
the
UPDATE_LOCK_TYPE= Data Set Option.
SCHEMA= LIBNAME Option
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.