Skip to main content
SQL Review automatically checks SQL against configured policies before execution. It is distinct from human approval, which is recorded in the Plan’s Issue. See the concept page for how checks work and how to interpret findings.

How It Works

When you create or edit a UI Plan, SQL Review checks its SQL and reports findings. Release-based Plans use SQL Review in CI instead of these Plan checks: column-required

Review Results

SQL Review results appear directly in the Plan interface, showing:
  • Errors: Must be fixed before the change can proceed
  • Warnings: Should be reviewed but won’t block execution
  • Passed checks: Confirmations that rules are satisfied

Configuring Review Policies

Review policies determine which rules are enforced for your database changes. You can configure these policies at the environment or project level.

Configure SQL Review Policies

Learn how to set up and customize SQL Review policies for your environments and projects

Review Rules Reference

Bytebase provides comprehensive review rules for each database engine, covering:
  • Schema design best practices
  • Performance optimization
  • Security requirements
  • Naming conventions

SQL Review Rules

Browse the complete list of available review rules for each database engine

Handling Review Feedback

When SQL Review identifies issues:
  1. Review the findings: Click on each issue to understand what needs to be fixed
  2. Update your SQL: Modify the statements to comply with the rules
  3. Re-run the review: The review automatically runs again when you save changes
  4. Proceed when cleared: Once all errors are resolved, continue with the approval process

Integration with Approval Flow

Inspect SQL Review findings before submitting the linked Issue with Ready for Review. The Review section shows the approval flow and discussion; automated findings remain in the Plan checks. Approval rules determine whether human approval is required. Passing SQL Review does not approve or deploy a change. See rollout requirements for the checks required before execution.