Skip to main content
A review policy is the basis for SQL auditing: it defines a set of enabled audit rules, along with each rule’s severity and parameter thresholds. The PawSQL Audit and Optimization modules share the same set of audit rule templates.
The same object has several names in the UI: the navigation and creation form show review template, the create button reads create rule template, some hints say rule configuration template, and some descriptions say audit rule set. This guide uses review policy throughout.

​
Global and local templates

  • Global templates: preset when the Audit platform is installed and visible to all users, one per database type (MySQL, Oracle, PostgreSQL, openGauss, DB2, DM, and others), each with 135–173 enabled rules. Global templates are read-only.
  • Local templates: created from a global template (or another visible template) and visible only to the creator and their team members. Local templates can enable or disable rules and adjust thresholds.

​
Rule categories

Rules are organized into three top-level categories — Object Design, Object Operation, and Data Operation — each divided into subcategories. See Manage Rules for the full classification.

​
Rule severity

Each audit rule has a severity that marks how serious its findings are, in three levels from lightest to most severe: notice, warning, critical. See Manage Rules.

​
In this section

Manage Review Policies

Manage Rules

Configure the SQL Quality Gate