13.07.2015 Views

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

25CHAPTER3Data Integrity and SecurityIntroduction to Data Integrity and Security 25DBMS Security 25Privileges 25Triggers 26<strong>SAS</strong> Security 26Securing Data 26Assigning <strong>SAS</strong> Passwords 26Protecting Connection In<strong>for</strong>mation 28Extracting DBMS Data to a <strong>SAS</strong> Data Set 28Defining Views and Schemas 29Controlling DBMS Connections 29Locking, Transactions, and Currency Control 30Customizing DBMS Connect and Disconnect Exits 31Potential Result Set Differences When Processing Null Data 31Introduction to Data Integrity and SecurityThis section briefly describes DBMS security issues and then presents measures youcan take on the <strong>SAS</strong> side of the interface to help protect DBMS data from accidentalupdate or deletion. This section also provides in<strong>for</strong>mation about how <strong>SAS</strong> handles nullvalues that help you achieve consistent results.DBMS SecurityPrivilegesThe database administrator controls who has privileges to access or update DBMSobjects. This person also controls who can create objects, and creators of the objectscontrol who can access the objects. A user cannot use DBMS facilities to access DBMSobjects through <strong>SAS</strong>/<strong>ACCESS</strong> software unless the user has the appropriate DBMSprivileges or authority on those objects. You can grant privileges on the DBMS side byusing the SQL pass-through facility to EXECUTE an SQL statement, or by issuing aGRANT statement from the DBLOAD procedure SQL statement.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!