Database Security

---

The access to a Pervasive.SQL database can be protected in several ways. Administrative-level security is set through the operating system. You can control who can administer a Pervasive.SQL database with the security mechanisms native to the operating system.

For transactional-only applications, database security is limited to file passwords called Owner Names. In order to access a specific data file, a user must supply the Owner Name for that file.

Pervasive.SQL also provides relational security at the user and group levels. You can control who can access the data and at what capability. For example, for each table within a Pervasive.SQL database, you can specify whether a user or group can create, select, update, insert into, delete, or alter the table.

You establish security by setting a password for the entire database. At that point, the only user authorized to access the database is a default user named Master. You can then add additional users and groups.

Security can be set within the PCC. Also supported are two Structured Query Language (SQL) statements pertaining to security: GRANT and REVOKE. GRANT and REVOKE also allow you to set security at the column level if you choose.

The GRANT syntax integrates with transactional Owner Names, allowing owner names to be enforced when using relational access.

See Chapter 7 for information pertaining to security, Owner Names, users, and groups.