SQL Server SQL review tools compared: the built-in SR rules in SQL projects, SqlServer.Rules' 140+ T-SQL checks, SQLFluff, tSQLt, Redgate, and where Bytebase's approval gate fits.

Top SQL Server SQL Review Tools in 2026

A SQL Server schema compare tool diffs two databases and generates the T-SQL to reconcile them. This 2026 guide reviews 8 tools and what each one costs.

Top 8 SQL Server Schema Compare Tools to Diff and Sync Databases in 2026

What the HIPAA Security Rule asks of database access: a name on every session, minimum necessary at the column, emergency access that still gets logged, and an audit trail that can say who read a patient's chart. The controls behind each, what OCR fines, and what the proposed 2027 rule tightens.

Database Access Control for HIPAA: The Security Rule at the Database

I followed Flyway's, Liquibase's, and Bytebase's own recommended quickstarts to a first managed PostgreSQL migration. Two took about half an hour. One took about an hour and a half.

From Zero to First Migration: How Much Setup Do Flyway, Liquibase, and Bytebase Require?

MySQL SQL review tools compared: SQLFluff for style, Skeema for schema-design linting, SOAR for query anti-patterns, and where Bytebase fits as the approval layer.

Top MySQL SQL Review and Lint Tools in 2026

What PCI DSS v4.0.1 asks of database access: least privilege by role, MFA on every CDE session, service accounts treated like humans, masked PANs, and a query-level trail kept for a year. Where each control lives, and where Bytebase stops.

Database Access Control for PCI DSS: Requirements 7, 8, and 10 at the Database

How PostgreSQL evolved from blocking DDL toward concurrent operations, metadata-only changes, and deferred constraint validation.

The Evolution of PostgreSQL Schema Migrations: Less Locking, Less Rewriting, Less Downtime

RDS IAM authentication replaces a stored database password with a 15-minute token. This reference implementation adds the rest of the JIT path: a scoped IAM role, verified identity, a bounded session, approval in Git, and an honest look at the four limits that remain.

Just-in-Time Database Access with AWS RDS IAM Authentication

Four missing primitives: delegation, attenuation, immutable application context, and labels on data. GRANT and RLS are a good policy engine, but nothing trustworthy feeds it when the caller is an AI agent. Oracle and SQL Server solved pieces of this; Postgres has none of it.

What Postgres is Missing for AI Agents

Bytebase and Delphix both mask sensitive data, but at different points: Delphix masks non-production copies, Bytebase masks live production queries.

Bytebase vs. Delphix: a tale of two data masking stories

Comparing HashiCorp Vault, Infisical, Doppler, and 1Password, the vendor-neutral options for database credentials that work across clouds and on-prem.

Best Secrets Manager for Database Credentials in 2026: Vault vs Infisical vs Doppler

On-behalf-of (OBO) is the pattern for AI agents to act with a caller's delegated identity instead of a shared credential. No mainstream database engine carries it the way agents need, and here is why a governance layer in front of the database is where it has to live.

On-Behalf-Of Database Access for AI Agents

Postgres SQL review tools compared: SQLFluff for style, Squawk for migration safety, plpgsql_check and pgTAP, and where Bytebase's rule engine overlaps them with an approval gate attached.

Top Dynamic Data Masking Tools in 2026

Compare direct database CLI access with a governed MCP server across six dimensions: setup, reach, identity, governance, auditability, and workflow fit.

MCP vs. CLI: How an AI Agent Should Reach Your Database

Zero trust for databases extends identity and network controls to SQL statements, query results, data changes, and schema changes.

Zero Trust for Databases: From Access Control to SQL Control

Snowflake and the data warehouses can tag any database object with structured metadata and drive masking from it. Almost no production database can. In the LLM era, that inline, self-contained context is exactly what agents need.

Object Tagging: The AI Feature Almost Every Production Database Skipped

DbUp runs your .NET migrations. Bytebase governs the database: change, access, and compliance in one platform. A practitioner comparison.

Bytebase vs. DbUp: from migration runner to unified governance

Database governance lives upstream, on the production database. Here is how to actually govern the source: reviewed changes, scoped access, codified policy, and audit where the data is born.

How to Govern Data at the Source: A Guide to Upstream Database Governance

Data governance and database governance are four letters apart and constantly conflated. They are different disciplines, owned by different teams, solved by different tools. Here is the dividing line.

Data Governance vs. Database Governance: The Difference Is the Base

PopSQL shuts down on September 1, 2026. Compare Bytebase and PopSQL across query collaboration, supported databases, access control, data masking, audit logging, and pricing before you migrate.

Bytebase vs. PopSQL: a side-by-side comparison for migrating teams

PopSQL shuts down on September 1, 2026. Compare the top PopSQL alternatives for team SQL editing, dashboards, and governed database access before you migrate.

Top PopSQL Alternatives 2026: Where to Migrate Before the Shutdown

The best multi-database MCP servers in 2026. Compare DBHub, Google's MCP Toolbox for Databases, and Bytebase on engine breadth, host neutrality, and governance for connecting AI agents to more than one database. Single-engine Postgres servers are covered in a companion post.

Top 3 Open Source Multi-Database MCP Servers in 2026

The best open source Postgres MCP servers in 2026. Compare Postgres MCP Pro, Supabase MCP, and pgconsole on host neutrality, access model, and governance for connecting AI agents to PostgreSQL. Multi-database MCP servers are covered in a companion post.

Bytebase vs. SchemaHero: a side-by-side comparison for database schema migration

Money software is judged not on whether the feature works, but on what the database can prove eighteen months later. Fintech database governance through three principles: no invented data, no lost data, no trust.

Database Governance for Fintech: Guarding the Ledger

PostgreSQL has no ADD COLUMN ... AFTER. The reason one little number in a system catalog turned a "simple" feature into a decade-long engineering saga, and what you can do about it today.

Why It's So Hard to Add a Column in the Middle of a PostgreSQL Table

What a database MCP server actually hands an AI agent, how a query runs through one, and why a raw connection-string server is fine on your laptop but risky against production.

What is a Database MCP Server?

Most database MCP servers hand an agent a connection string and call it a day. The MCP server is the one place agent database access is governed or wide open.

Governed MCP vs. Raw MCP: How Agents Reach Your Database

AI agents are no longer just reading your database, they are authoring the migrations. The write path is a different risk class, and it needs its own gate.

When the Agent Writes the Migration, Who Approves It?

Generic PAM controls the database connection. Database PAM controls the SQL statement: per-query authorization and approval, SQL review, data masking, and statement-level audit. What the category means and why it exists.

What is Database PAM (Privileged Access Management)?

How to run SQL Server schema migrations safely in production, covering state-based vs migration-based workflows, online index operations, batched backfills, the expand-and-contract pattern, and CI/CD.

SQL Server Schema Migration and Change Management

CyberArk is a broad privileged access management (PAM) platform. Bytebase is a database-specific PAM for access control, masking, and SQL review. If you already run CyberArk, here is why you still need it for the database.

Bytebase vs. CyberArk: the database vertical in your PAM stack

Database credentials management best practices: store passwords and secrets in one place, rotate on a schedule, and separate the application path from the human path.

Database Credentials Management: Best Practices

The practical ways to audit MySQL activity, from the general query log to audit plugins, binlog CDC, and Bytebase, and where each one falls short.

MySQL Audit Logging Guide

Every critical asset has its system of record, except the database. Bytebase is the one. The standard for database development.

The Standard for Database Development

Dynamic data masking is chosen by access path, not product. Five approaches (engine-native, in-database, application, BI layer, and Bytebase) and which caller each one masks.

How to Implement Dynamic Data Masking: Five Approaches by Access Path

Static vs dynamic data masking, when each applies, how they differ on backups, performance, and reversibility, and when to run both.

Static vs Dynamic Data Masking: When to Use Which

The static data masking tools that produce safe non-production data, Delphix, Tonic.ai, and greenmask compared, plus how to roll your own when no tool fits.

Static Data Masking Tools (and How to Roll Your Own)

Compare BigQuery data masking options: native column-level dynamic data masking (built-in masking rules via policy tags and data policies, Dataplex catalog) and Bytebase fleet-wide masking.

BigQuery Dynamic Data Masking

Compare SQL Server data masking options, native Dynamic Data Masking (five mask types, SQL Server 2022 granular UNMASK) and Bytebase fleet-wide masking.

SQL Server Dynamic Data Masking

Compare Oracle data masking options. Native Data Redaction (five function types via DBMS_REDACT, EXEMPT REDACTION POLICY) and Bytebase fleet-wide masking.

Oracle Dynamic Data Masking

You write a one-line UPDATE against production. Here's the lane that keeps it safe: the four phases, the controls, and what each one prevents.

How to Handle Ad-hoc Database Data Changes?

Notes on the MySQL 9.7 LTS release: Hypergraph Optimizer in Community, JSON Duality View DML, Group Replication observability, and Dynamic Data Masking for Enterprise.

Notes on the MySQL 9.7 LTS release

Most DAC implementations stop at the connection. Real DAC operates at the statement and covers three vectors: machine, human, and AI agent.

What is Database Access Control (DAC)?

How to run dynamic data masking so it survives an audit: mask by role, go column-level, log unmask events, review policy changes in code, and keep environments in sync. Plus a vendor comparison and an end-to-end walkthrough.

Dynamic Data Masking Best Practices

How Bytebase audits the workflow layer: every SQL, schema change, approval, and export tied to a real user identity, with structured exports for any SIEM.

How Bytebase Handles Audit Logging

PostgreSQL 19 features I'm excited about: planner advisor framework, DDL extraction, online REPACK, pg_stat_recovery, parallel autovacuum, sequence sync, and 64-bit MultiXact.

PostgreSQL 19 features I'm excited about

Bytebase is HIPAA-compliant — independent verification that our administrative, physical, and technical safeguards meet the HIPAA Security Rule for handling Protected Health Information.

HIPAA Compliance

PAM tools gate the database connection. Databases also need SQL review, a schema change workflow, and per-statement approval. Here is where PAM stops and why most teams run it alongside Bytebase.

Bytebase vs. PAM: Why Database Teams Need More Than Privileged Access Management

What SOC 2 compliance audits actually want from your database audit log: not 'logging enabled' but evidence your auditor will accept. Lessons from going through our own audit.

SOC 2 Audit Log Requirements: Lessons From Our Own Audit

A side-by-side look at Bytebase and Atlas for database schema migration: how each one approaches migrations, their CI/CD and access control, supported databases, and what they cost. Updated for Atlas v1.1 and Bytebase 3.16.

Bytebase vs. Atlas: a side-by-side comparison for database schema migration

Database access control practices that hold up in a SOC 2 audit: least privilege, separation of duties, just-in-time access, statement-level enforcement, and the common mistakes that get flagged.

Database Access Control (DAC) Best Practices

A practical look at what SOX Section 404 expects from database changes: the four ITGC domains, the six questions auditors actually ask, and how to make compliance evidence a byproduct of your workflow.

Database Change Management for SOX Compliance

TRUNCATE and DELETE both remove rows, but they differ in speed, rollback behavior, and locking. Here is how each one behaves in PostgreSQL, MySQL, and SQL Server, and when to reach for which.

TRUNCATE vs DELETE in SQL: Differences Across PostgreSQL, MySQL, and SQL Server

A practical walk through six database design patterns you will actually meet in production: normalization, star schema, EAV, polymorphic associations, multi-tenancy, and the anti-patterns worth avoiding.

Database Design Patterns Every Developer Should Know

A practical walkthrough of pgvector: installing the extension, storing embeddings, writing similarity queries, building HNSW indexes, and knowing when plain PostgreSQL is enough.

pgvector: How to Add Vector Search to PostgreSQL

How upsert works across MySQL, PostgreSQL, and SQL Server, with the syntax for each, the edge cases worth knowing before you ship, and how upserts interact with migrations.

Upsert in SQL: INSERT ON DUPLICATE KEY vs ON CONFLICT Explained

AI agents need more than DDL. The full database lifecycle codified (schema, dependencies, ownership, history) gives LLMs the context to query correctly.

From Schema as Code to Schema as Context

How to find and fix slow MySQL queries: reading the slow query log, using EXPLAIN, tuning indexes, and rewriting queries, with a worked example for each.

How to Fix Slow MySQL Queries: A Practical Guide

Convex and Supabase are both backend-in-a-box platforms, but built on different foundations. This post compares their architecture, real-time model, data model, schema management, and pricing to help you decide.

Convex vs Supabase: Which Backend Platform Should You Choose?

Blue-green deployment is easy when your servers are stateless. The trouble starts at the database. This guide walks through why database blue-green is hard and how to do it without corrupting your data.

Database Blue-Green Deployment: A Practical Guide

A look at 10 data management tools developers and data engineers actually use in 2026: GUI clients, schema migration, pipelines, and analytics, with pricing for each.

Top 10 Data Management Tools in 2026

How to give AI agents governed access to your databases. Identity, authorization, query control, audit, and masking, applied to a new principal type.

How to Govern AI Agent Database Access

The best SQL editors built exclusively for PostgreSQL: what each one is good at, who it fits, and when a Postgres-only tool beats a multi-database client.

Enterprise Text-to-SQL: Context, Evaluation, and Governance

A practical look at the database deployment tools DevOps teams actually use in 2026 — Flyway, Liquibase, Atlas, pgschema, Octopus Deploy, Harness, DBmaestro and Bytebase — sorted by how each one defines, applies, and coordinates schema changes.

Database Deployment Tools for DevOps Teams in 2026

A walk-through of how renaming a single column can quietly break an analytics pipeline, why it happens, and how schema change detection and notification help you catch it early.

Schema Change Detection and Notification: Why a Simple Column Rename Can Break Your Data Pipeline

How to read a Postgres query plan, spot the common performance problems, and fix them without breaking other queries.

Postgres Query Plan: How to Read and Fix Performance Issues

A walk through every layer of the Postgres permission system that can raise ERROR 42501, why each one fires, and how the behavior differs from MySQL.

The Anatomy of Postgres Permission ERROR 42501

A practical look at Postgres logs: what they record, how the logging collector works, which parameters actually matter in production, and the mistakes that turn logs into expensive noise.

Postgres Logs Explained: A Practical Guide for Production

Postgres 19 widens MultiXactOffset to 64 bits, eliminating the hidden 4 billion member limit that caused catastrophic outages for high-concurrency workloads.

Postgres 19 Feature Preview: 64-bit MultiXactOffset

How to run MySQL schema migrations without blocking queries or causing downtime, covering the MySQL-specific behaviors that bite in production and the tools that work around them.

MySQL Schema Migration Best Practice

Postgres 19 introduces automatic sequence synchronization for logical replication, eliminating manual tracking and making major version upgrades and failover significantly easier.

Postgres 19 Feature Preview: Sequence Synchronization for Logical Replication

What multi-environment database deployment actually involves, the problems teams keep hitting, and the patterns (manual scripts vs GitOps) for handling them.

Database Multi-Environment Deployments - The Challenges and Patterns

A guide to open source sensitive data discovery tools, from NLP libraries like spaCy and Microsoft Presidio to multi-source scanners like Hawk-Eye and full metadata platforms like OpenMetadata.

Top Open Source Sensitive Data Discovery Tools in 2026

Database audit logging really has two layers: the infrastructure layer your cloud provider ships, and the workflow layer you have to build yourself. Here is what each one captures, and why an audit needs both.

Database Audit Logging: Two Layers, One Trail

A practical guide to HITRUST database compliance covering access control, audit logging, change management, and data protection.

Database Compliance for HITRUST: Controls, Risks, and Best Practices

What the "Require Primary Key" SQL review rule checks, the production problems a missing primary key tends to cause, and the SQL to fix tables that don't have one.

Require Primary Key: A SQL Review Rule Explained

What the "Enforce NOT VALID in CHECK" SQL Review rule does, why adding a CHECK constraint can lock your table, and how the two-step NOT VALID approach avoids it.

Enforce NOT VALID in CHECK: A SQL Review Rule Explained

The practical ways to audit a PostgreSQL database, from native logging to triggers, logical replication, pgAudit, and Bytebase, with the trade-offs of each.

Postgres Audit Logging Guide

Learn why CASCADE operations in SQL can lead to catastrophic data loss and how the "Prohibit CASCADE" review rule protects your production database.

Prohibit CASCADE: A SQL Review Rule Explained

A walkthrough of moving each Supabase piece (database, auth, storage, functions, realtime, networking) to its AWS counterpart, with a services-first order that keeps the final database cutover simple.

How to Migrate from Supabase to AWS

Six open-source PostgreSQL backup tools compared for 2026, with the language, license, interface, and best-fit use case for each, plus a note on which ones are still maintained.

What is Enterprise Database Management (EDM)?

A plain explanation of Postgres Transaction ID (XID) wraparound: what causes it, how to check how close you are, and what keeps it from taking your database offline.

Postgres Transaction ID (XID) Wraparound

How a CI/CD pipeline for database schema migration works end-to-end. What it gates, what it leaves outside, and the tools that fit.

How to Build a CI/CD Pipeline for Database Schema Migration

A practical guide to shipping features with PostgreSQL, covering my day-to-day development workflow, the tools I actually use, and real-world examples

How I Ship Features with Postgres

What LGPD means for database operations: how it actually differs from GDPR, what the ANPD sanctions in practice, and the database controls (classification, masking, retention, audit) that hold up.

Database Compliance for LGPD: Implications and Best Practices

What a Postgres LATERAL JOIN does, when to reach for one, and the patterns and gotchas you'll run into using it.

What is Postgres LATERAL JOIN?

What MySQL Online DDL actually does, how its three algorithms (INSTANT, INPLACE, and COPY) differ, and the limitations to plan around before you run a schema change in production.

MySQL Online DDL: A Practical Guide

The best open-source Postgres connection poolers in 2026. Compare PgBouncer, Odyssey, PgDoorman, and PgDog — with our pick: PgBouncer if you want free, PgDog if you want a commercial vendor.

SQL Table Naming Dilemma: Singular vs. Plural

PostgreSQL 18 features that change how application developers write and ship code.

What's New in PostgreSQL 18: A Developer's Perspective

Compare Snowflake Dynamic Data Masking with database views and Bytebase fleet-wide masking on edition gate, policy management, and audit trail.

Snowflake Dynamic Data Masking (DDM) and Alternatives

A look at the open-source ways to add authentication and authorization to a Postgres app in 2025, from all-in-one platforms to libraries, identity servers, and the minimalist JWT-to-RLS pattern, with a "best for" note on each.

Postgres Case Sensitivity Explained

What pg_database_owner does in Postgres, why it was added, and how to use it without hitting the "cannot have explicit members" error.

What is pg_database_owner in Postgres

A reference for which Postgres DDL operations rewrite the whole table (and take heavy locks) versus which ones are metadata-only, plus how to test it yourself before you run it in production.

Which Postgres Operation causes a table rewrite

A practical rundown of the Postgres Row-Level Security traps that quietly break performance or leak data, with the fix for each.

Postgres Row-Level Security Footguns


<HintBlock type="info">

This post is maintained by Bytebase, an open-source database governance platform. We update the post periodically.

</HintBlock>

SQL Server's review tooling is shaped differently from MySQL's or Postgres's, and not because T-SQL needs less of it. Microsoft ships static analysis inside its own build toolchain, so the baseline is free, first-party, and already installed for anyone using a SQL project. The strongest community option extends that same rule model rather than competing with it. What's thin is everything in between: fewer independent open source linters than Postgres has, and two names that still show up in every "SQL Server SQL review" search stopped shipping entirely.

What are the criteria? Every pick here is:

- **T-SQL-aware** - general SQL linters that treat T-SQL as an afterthought are noted, but the picks below either target SQL Server specifically or have real T-SQL dialect coverage.
- **Actively maintained, or the gap disclosed if not** - checked against commit and release history, not a marketing page. One pick below has not cut a release since 2022, and that is stated in its own section rather than buried. The tools that fail the check outright are named below as failures, not recommendations.
- **Adoptable on its own** - no pick requires the others to be useful.

## Built-in SQL code analysis (SQL Database Projects)

If your schema lives in a SQL project, you already have a linter and it is off by default. SQL Database Projects ship 14 rules under `Microsoft.Rules.Data`, split across the same three categories every other tool on this list uses: design, naming, and performance. It applies to projects targeting SQL Server, Azure SQL Database, Azure SQL Managed Instance, and Fabric SQL database.

The design rules are the ones worth turning on first. `SR0001` flags `SELECT *` in stored procedures, views, and table-valued functions. `SR0008` catches `@@IDENTITY` where `SCOPE_IDENTITY` is almost always what you meant, which is a correctness bug that only shows up once a trigger exists. `SR0013` finds an output parameter that isn't populated on every code path. `SR0010` catches the deprecated `*=` join syntax. On the naming side, `SR0016` is the `sp_` prefix rule — SQL Server checks the master database first for any procedure named that way, no matter how you qualify it. On performance, `SR0005` flags a `LIKE` pattern starting with `%`, and `SR0004` an unindexed column as the test expression in an `IN` predicate.

Enabling it is a project property, and a rule can be disabled with `-` or promoted from warning to error with `+!`:

```xml
<PropertyGroup>
  <RunSqlCodeAnalysis>True</RunSqlCodeAnalysis>
  <SqlCodeAnalysisRules>-Microsoft.Rules.Data.SR0006;+!Microsoft.Rules.Data.SR0008</SqlCodeAnalysisRules>
</PropertyGroup>
```

The same settings override from CI with `dotnet build /p:RunSqlCodeAnalysis=True`, and per-file exceptions go in a `StaticCodeAnalysis.SuppressMessages.xml` rather than a comment someone deletes later. Configuration used to mean hand-editing the `.sqlproj`; the VS Code SQL Database Projects extension added a Code Analysis Settings dialog in 2026, with per-category toggles and a Warning/Error/None dropdown per rule. SSMS and Visual Studio expose the same thing under project properties.

Two limits. It analyzes the project model, so a script you're about to run by hand isn't covered — only what's in the project. And 14 rules is a floor: nothing here knows about locking or migration safety, the performance rules stop at a handful of predicate patterns, and there's no index-hygiene coverage at all.

**Best for:** any team already building a SQL project. It's one property away, and there's no reason to leave it off.

## SqlServer.Rules and T-SQL Analyzer

[SqlServer.Rules](https://github.com/ErikEJ/SqlServer.Rules) is the same idea at roughly ten times the coverage: 140+ rules, MIT-licensed, built on the same code-analysis extensibility model Microsoft's 14 rules use. It re-covers the built-in basics and keeps going — `SRD0002` for a missing primary key, `SRD0004` for a foreign key with no supporting index, `SRD0003` for a primary key that's too wide, `SRP0001` for views stacked on views, `SRN0006` for two-part object naming.

The 2026 change is where it runs. This used to be a build-time NuGet package and nothing else. It now also ships as the T-SQL Analyzer extension, which analyzes plain `.sql` files live in the editor — stored procedures, queries, migration scripts, ad-hoc SQL — with no build step and no SQL project required. Visual Studio and SSMS 22 got it in June 2026, VS Code in August 2026. Rules are configured with the same expression syntax Microsoft's MSBuild property uses (`-SqlServer.Rules.SRD0004` to disable, `+!SqlServer.Rules.SRN0005` to promote to error), and `tsqlAnalyzer.sqlVersion` pins the target version — `Sql160`, `Sql170`, `SqlAzure` — so the analysis matches the server you actually deploy to. There's also a CLI and an MCP server for driving the same rules from GitHub Copilot.

The build-time package, `ErikEJ.DacFX.SqlServer.Rules`, is still there and works with `MSBuild.Sdk.SqlProj`, `Microsoft.Build.Sql`, and classic `.sqlproj` projects alike, so adopting it doesn't force a project conversion first.

What it can't do is look at your data. The foreign-key index rule and its neighbors are static heuristics against the statement and the model; the analyzer doesn't know your row counts or index statistics, so the same finding on a 200-row lookup table is noise you'll want to suppress. Worth knowing too: it's a single-maintainer community project, forked from an earlier one, and the whole 140-rule set rests on that.

**Best for:** the deepest T-SQL-specific coverage available, free, whether your SQL lives in a project or in loose scripts.

## SQLFluff (T-SQL dialect)

[SQLFluff](https://sqlfluff.com/) is a style linter, not a safety linter, and it's the only pick here that treats SQL as text rather than as a database model. It parses casing, indentation, and formatting against the `tsql` dialect and enforces one house style in CI. Its dialect coverage is real but not complete: the cast-style rule, for one, only handles the two-argument form of `CONVERT`, because T-SQL's three-argument version — the one that takes a style code — has no `CAST` equivalent to rewrite into.

Because it never builds a model of the database, it has no idea that a stored procedure calls another stored procedure, or that a view sits on top of three other views. Style and structural safety are different layers, and SQLFluff only covers the first.

**Best for:** enforcing one SQL style across a team, in CI, before it ever reaches a human reviewer.

## tSQLt

[tSQLt](https://tsqlt.org/) is a testing framework, not a linter, and belongs on this list for the same reason pgTAP does on the Postgres one. Instead of flagging a statement as risky, you write test procedures with `tSQLt.AssertEquals`, `tSQLt.ExpectException`, and similar assertions, and run them against the schema the way you'd run unit tests against application code. It runs entirely inside SQL Server via T-SQL, tests execute in a transaction that rolls back automatically, and output comes in plain text or XML for CI. It's Apache-2.0.

The maintenance picture needs stating plainly, because it's the one pick here that doesn't cleanly pass the criterion above. The last published release, V1.0.8043.39707, is from August 2022 — four years ago. The repository still sees commits, most recently in 2026, and the framework works fine on current SQL Server versions. But a project that commits without releasing is one where you're choosing between a four-year-old build and a source checkout, and that's worth knowing before you make it part of your pipeline.

Where it still earns its place: proving a migration produced the schema you intended, not just that it applied without an error. A migration that silently skips a step because of a typo'd table name passes every linter on this list and fails the first tSQLt assertion that checks for the column.

**Best for:** schema changes complex enough that "it ran without an error" isn't proof it's correct.

## Redgate SQL Prompt (SQL Code Analysis)

[Redgate SQL Prompt](https://www.red-gate.com/products/sql-prompt/) bundles a static analysis feature called SQL Code Analysis, covering best-practice, deprecated-syntax, naming, performance, and style rule categories, checked as you type in SSMS or Visual Studio. The history is worth naming: this used to be a separate free tool, SQL Code Guard, distributed as its own SSMS add-in. [Redgate deprecated the standalone add-in and folded its rule set into SQL Prompt](https://documentation.red-gate.com/scg/sql-code-analysis-documentation/sql-code-guard-ssms-2016-add-in-deprecated) — the free, unbundled version is gone, and the functionality now requires the SQL Prompt license.

That's IDE-integrated linting, not a CI gate on its own. Running it unattended against a pull request means scripting the command-line analysis path Redgate ships alongside it, rather than relying on the interactive SSMS experience.

**Best for:** teams already on SQL Prompt for autocomplete and formatting who want the linting layer included rather than a second tool.

## Tools you'll see recommended and shouldn't rely on

**ApexSQL Complete and ApexSQL Refactor are discontinued.** Quest — which owns the ApexSQL line — ended support for both on December 31, 2025, along with the ApexSQL Fundamentals Toolkit that packaged them, and is [steering existing customers to Toad for SQL Server](https://support.quest.com/product-notification/noti-00001585) instead. Refactor had already stopped being freely updated years earlier, when new versions started requiring a Toolkit license. If either still shows up in a "best SQL Server tools" list dated 2026, that list hasn't been rechecked.

**SonarQube's dedicated T-SQL plugin has been dead longer than that.** SonarSource's own SonarTSQL plugin was last updated in May 2019 and is formally deprecated. The community successor, [gretard/sonar-sql-plugin](https://github.com/gretard/sonar-sql-plugin), covers T-SQL alongside MySQL, Postgres, Snowflake, and Vertica, but its last tagged release was February 2024. SonarQube Developer Edition and above now ships built-in T-SQL analysis directly, which is the path to take if T-SQL needs to land in the same Sonar dashboard as everything else; the standalone plugin route is the one to skip.

## Bytebase

[Bytebase](https://www.bytebase.com/sql-review/) is where many teams end up putting the review itself, because one rule engine and approval workflow covers MySQL, Postgres, SQL Server, and 20+ other engines from a single console, rather than a different tool per engine.

Where this is honest rather than uniform: the [published rule library](https://docs.bytebase.com/sql-review/review-rules) documents 80+ MySQL-specific and 50+ Postgres-specific rules by name. SQL Server runs through the same review-and-approval workflow — connect an instance, attach a review policy scoped to an environment or project, and every change routes through the same issue a DBA approves — but the SQL-Server-tagged rule set isn't published at that granularity. Rule levels attach to an environment or a project, with the project-level policy taking priority, so the same rule can warn in dev and block in prod. It also runs as a [GitHub check](/blog/integrate-sql-review-into-github/) if you'd rather keep the gate in the pull request.

The practical split on SQL Server: T-SQL Analyzer gives you 140+ engine-specific checks and no opinion about who's allowed to run the change; Bytebase answers the second question and doesn't currently match the first. Run both.

**Best for:** teams that want one approval workflow across SQL Server and their other engines, paired with a dedicated T-SQL linter for anti-pattern depth.

## Comparison

| Tool | Layer | Scope | Status (2026) | License |
| --- | --- | --- | --- | --- |
| Built-in SQL code analysis | Design + naming + perf lint | SQL project (build) | 14 rules, ships with the tooling | Free with the tooling |
| SqlServer.Rules / T-SQL Analyzer | Design + naming + perf lint | `.sql` files or project | 140+ rules, live in-editor since 2026 | Open source (MIT) |
| SQLFluff (tsql) | Style | SQL text | Monthly releases | Open source (MIT) |
| tSQLt | Testing | Schema assertions | Last release Aug 2022, commits in 2026 | Open source (Apache-2.0) |
| Redgate SQL Prompt | Style + best-practice lint | SQL text (IDE) | Commercial release | Commercial |
| Bytebase | Policy + approval workflow | Change workflow | One engine across 20+ databases | Free (Community) / paid tiers |

Read the table by what's missing from your stack, not by which row lists the most rules. A team on the built-in 14 rules has a floor and no depth. A team on T-SQL Analyzer has strong static coverage and no approval gate. A team on Bytebase alone has the gate and a thinner T-SQL rule set than a dedicated linter. These stack; they don't compete.

## Picking one

Turn on the built-in code analysis first. If you build a SQL project, it costs one property and catches the `@@IDENTITY` and `SELECT *` class of problem today. Then add T-SQL Analyzer, which is the single highest-value pick on this list: free, 140+ T-SQL rules, and since 2026 it works on loose `.sql` files in the editor, so it no longer matters whether your schema is in a project at all.

SQLFluff is the next add if style consistency is the recurring code-review argument, and it's nearly free to turn on. tSQLt is a narrower bet with a real caveat: reach for it when a migration's correctness matters more than whether it merely avoided an error, and go in knowing the last release is from 2022. Redgate SQL Prompt makes sense for shops already paying for it. Skip ApexSQL Complete/Refactor and the standalone SonarQube T-SQL plugin no matter how often they still turn up in search results.

Bytebase is the layer to add once the question shifts from "is this SQL safe" to "who approved it before it ran." On SQL Server that's a pairing, not a replacement — the linters own the anti-patterns, Bytebase owns the gate and the audit trail.

For the three-layer framework this list assumes — linting, semantic rules, policy — [SQL review: from linting to governance](/blog/sql-review-tool-for-devs/) is the place to start. The same comparison exists for [MySQL](/blog/top-mysql-sql-review-tools/) and [Postgres](/blog/top-postgres-sql-review-tools/) if you run a mixed estate.


The
Bytebase Blog

What Postgres is Missing for AI Agents

Zero Trust for Databases: From Access Control to SQL Control

Object Tagging: The AI Feature Almost Every Production Database Skipped

Explore the standard for database governance

Solutions & Platform

Resources

Change Management

Access & Security

AI & Agents

Comparisons

Company

Legal

The Bytebase Blog

What Postgres is Missing for AI Agents

Zero Trust for Databases: From Access Control to SQL Control

Object Tagging: The AI Feature Almost Every Production Database Skipped

Explore the standard for database governance

The
Bytebase Blog