Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

TSQLLint review

Free#5 of 25 in SQL Linters and Formatters

A configurable, free T-SQL linter with autofix and plugin support.

8.4/10Editor score
Visit TSQLLint
TSQLLint8.4 Visit TSQLLint

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

TSQLLint is an open-source command-line linter for Transact-SQL scripts. It is designed for developers and teams working with SQL Server who want configurable anti-pattern detection, reporting, and automatic fixing for supported violations. The tool runs on Windows, macOS, and Linux, and can lint individual files, directories, or wildcard paths. Its free, open-source model makes it suitable for projects that want a focused T-SQL quality tool without a paid plan.

Configuration is the main strength. Projects can define rules in a .tsqllintrc file, set each rule to off, warning, or error, and use inline rule disabling or compatibility-level overrides when exceptions are needed. TSQLLint also supports custom .NET plugins, giving teams a way to extend its checks beyond the built-in anti-pattern rules. The Visual Studio Code extension and compatibility with SQL Server Management Studio external tools help fit linting into common SQL development environments. Distribution through the .NET tool system, Homebrew, and npm adds flexibility for installation across supported platforms.

TSQLLint is a strong match for T-SQL-focused teams that value control over rule behavior and want autofix where available. Its scope is narrower than tools built for several SQL dialects, since its documented focus is Transact-SQL and SQL Server compatibility levels. Teams looking for broad cross-database linting should consider a multi-dialect alternative instead. It is also better suited to organizations comfortable managing configuration and, when needed, custom .NET plugins than to buyers seeking a managed service with a broader surrounding platform. For focused SQL Server development, its combination of open-source access, configurable severity, editor support, and extensibility is practical.

TSQLLint pros and cons

  • Where it wins
    • Configurable rule severities and automatic fixes for supported violations
    • Runs across files, directories, and wildcard paths
    • Supports custom .NET plugins and Visual Studio Code
  • Where it doesn't
    • Focused on T-SQL rather than multiple SQL dialects
    • Advanced customization requires .NET plugin development
    • CI coverage is less established than its editor and local workflows

TSQLLint fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update