Skip to main content
When creating a review ticket, pick a matching policy from the “review policy” dropdown (the interface may label it “review template”). The right policy gives comparable work a consistent standard and keeps irrelevant database or environment checks out of the result set. The definition of a policy, default and custom templates, and rule and threshold management are covered in Rules and Quality Policy.

​
Goal

Choose a review policy that matches the target database engine, environment, and workflow, so comparable SQL uses a consistent standard.

​
Prerequisites

Know the target database engine, version, environment, and intended review purpose before selecting a policy.

​
Selection order

Evaluate candidate policies in this order:
  1. Match the target database engine and version.
  2. Match the environment, such as development, test, or production.
  3. Match the workflow, such as developer feedback, release review, or remediation.
  4. Verify ownership, visibility, and the responsible maintainer.
  5. Review rule severities, parameters, and thresholds.

​
Inspect the policy before use

Verify at least the following:
  • supported database engines and versions;
  • policy status and most recent update;
  • enabled and disabled rules;
  • severity assigned to each rule;
  • configurable limits such as length, count, duration, or affected rows;
  • documented exceptions or exclusions;
  • policy scope within the current organization or project.
Policies with the same display name can still differ by project, revision, or update date. For a formal review, verify the policy identity rather than relying on its name alone.

​
If a policy is unavailable

​
Expected Result

The selected policy’s rules, severities, and thresholds match the target database and workflow, avoiding irrelevant checks in the result set. After understanding the policy, return to Create a Review Ticket. See Rules and Quality Policy for creating and maintaining policies.