21
CHAPTER
3
Data Integrity and Security
Introduction to Data Integrity and Security
21
DBMS Security
21
Triggers 22
SAS Security
22
Assigning SAS Passwords
22
Protecting Connection Information 23
Extracting DBMS Data to a SAS Data Set
24
Defining Views and Schemas
24
Controlling DBMS Connections
25
Locking, Transactions, and Currency Control
26
Customizing DBMS Connect and Disconnect Exits
26
Potential Result Set Differences When Processing Null Data
27
Introduction to Data Integrity and Security
This section briefly describes DBMS security issues and then presents measures you
can take on the SAS side of the interface to help protect DBMS data from accidental
update or deletion. This section also provides information about how SAS handles null
values that will help you achieve consistent results.
DBMS Security
The database administrator (DBA) controls who has privileges to access or update
DBMS objects. The DBA also controls who can create objects, and creators of the
objects control who can access the objects. A user cannot use DBMS facilities to access
DBMS objects through SAS/ACCESS software unless the user has the appropriate
DBMS privileges or authority on those objects. You can grant privileges on the DBMS
side by using the Pass-Through Facility to EXECUTE an SQL statement, or by issuing
a GRANT statement from the DBLOAD procedure SQL statement.
On the DBMS, you should give users only the privileges they must have. Privileges
are granted on whole tables or views. A user must explicitly be granted privileges on
the DBMS tables or views that underlie a view in order to use that view.
Note: See your DBMS documentation for more information about ensuring security
on the DBMS side of the interface.
