# SQL Review

> SQL review in three layers: linting catches typos, semantic rules catch anti-patterns, approval workflows catch policy violations. Tools, rules, and integration with GitHub and GitLab.

Source: https://www.bytebase.com/sql-review/

---

## Linted. Reviewed. Approved.

Catch bad SQL before it ships. Linting catches typos. Semantic rules catch anti-patterns. Approval workflows catch policy violations.

## Three layers. One review.

### Linting

Syntax and style. Catches typos, formatting violations, and dialect mistakes before the SQL ever reaches the database.

### Semantic rules

Schema-aware checks. Require primary keys, prohibit destructive cascades, enforce naming conventions, flag missing indexes.

### Policy with approval

Role-based human review. Production changes route to a DBA; lower environments auto-approve; break-glass paths leave an audit trail.

## Read in order.

### Why SQL review

When strict requirements help and when they get in the way. /blog/is-sql-review-necessary

### From linting to governance

The three layers, and the tool comparison. /blog/sql-review-tool-for-devs

### SQL review in GitHub

Three integration paths: GitHub Action, GitHub App, GitOps CI. /blog/integrate-sql-review-into-github

## Get Started

- [Contact us](https://www.bytebase.com/contact-us/)
- [Start now (cloud)](https://console.bytebase.com)
