Database administrators control who has privileges to access or update DBMS objects. They also control who can create objects, and object creators control who can access the objects. Users cannot use DBMS facilities to access DBMS objects through SAS/ACCESS software unless they have the appropriate DBMS privileges or authority on those objects. You can grant privileges on the DBMS side by using the SQL pass-through facility to EXECUTE an SQL statement or by issuing a GRANT statement from the DBLOAD procedure.
You should give users only the privileges on the DBMS that they must have. Privileges are granted on whole tables or views. You must explicitly grant user privileges on the DBMS tables or views that underlie a view so that users can use that view.
For more information about ensuring security on the DBMS side of the interface, see your DBMS documentation.
If your DBMS supports triggers, you can use them to enforce security authorizations or business-specific security considerations. Triggers are executed based on when the SQL statement is executed and how often the trigger is executed. Triggers can be executed before an SQL statement is executed, after an SQL statement is executed, or for each row of an SQL statement. Also, triggers can be specified for DELETE, INSERT, and UPDATE statement execution.
Enabling triggers can provide more specific security for Delete, Insert, and Update operations. SAS/ACCESS abides by all constraints and actions that are specified by a trigger. For more information, see the documentation for your DBMS.