TSQLLint
github.com
- Free plan
- Windows
- macOS
- Linux
- Browser extension
What TSQLLint is
TSQLLint identifies and reports anti-patterns in T-SQL scripts. Its rules can be set to off, warning, or error; a violation configured as an error returns a non-zero exit code. The command-line tool can fix problems it recognizes as auto-fixable with the --fix or -x option. Users can set configuration in a .tsqllintrc file, or use the in-memory default configuration when no file is found. Listed SQL Server compatibility levels are 80, 90, 100, 110, 120, 130, 140, and 150. Custom .NET plugins are supported if they implement TSQLLint's IPlugin interface and target net6.0. Before lint rules run, placeholders in SQL files are replaced with values supplied through environment variables. Official installation methods include dotnet-tool, Homebrew, and NPM. The VS Code extension underlines possible problems in opened .sql files for inspection on hover, while SQL Server Management Studio can invoke TSQLLint through External Tools. The software is free under the MIT License and focuses on T-SQL scripts.
Who it suits
TSQLLint suits people working with T-SQL scripts who want configurable checks for undesirable patterns. It offers command-line, VS Code, and SQL Server Management Studio workflows.
Good to know, and what to watch
- Rules can be set to off, warning, or error.
- Can automatically fix problems it marks as fixable.
- Supports custom .NET plugins.
- Offers dotnet-tool, Homebrew, and NPM installation.
- Includes VS Code and SSMS integration options.
- Scope is limited to T-SQL.
- Custom plugins must target net6.0 and implement IPlugin.
Plans
Every plan and priceTSQLLint
Free plan
Getting started
- Open the TSQLLint project website
- Install it through dotnet-tool, Homebrew, or NPM
- Create a .tsqllintrc file or use the in-memory defaults
- Configure rules and SQL Server compatibility level
- Use the VS Code extension or SQL Server Management Studio External Tools integration
Limits to check
TSQLLint is free. Its documented SQL compatibility options are limited to the listed SQL Server levels, and custom plugins must target net6.0.
The Club's review
TSQLLint is a focused linter for Transact-SQL scripts, aimed at developers and database teams maintaining SQL Server code. It suits readers who want configurable anti-pattern checks, command-line enforcement, and editor feedback without paying for a license.
Overview
TSQLLint examines T-SQL and reports undesirable patterns rather than trying to serve as a general SQL formatter. Rules can be set to off, warning, or error. An error produces a non-zero exit code, making the tool practical for automated checks that must reject scripts with serious violations. The T-SQL-only scope is a strength for SQL Server work but a poor fit for teams sharing code across other dialects.
Configuration is optional. A .tsqllintrc file lets teams define their policy, while an in-memory default configuration is used when no file is present. SQL Server compatibility levels 80, 90, 100, 110, 120, 130, 140, and 150 are supported. Before lint rules run, placeholders in SQL files are replaced with values supplied through environment variables, which helps scripts that rely on deployment-time substitutions.
Key features
Checks and automated correction
The command-line tool can fix findings identified as auto-fixable with --fix or -x. That can shorten cleanup for routine violations, although findings without a safe automated correction still require manual changes. Severity controls let the same rule act as a reminder during development or a hard gate in automation.
Custom extensions
Custom .NET plugins extend coverage beyond built-in rules. A plugin must implement TSQLLint's IPlugin interface and target net6.0. This is useful when an organization has internal standards, but it also puts the extension work and .NET compatibility burden on the team adopting it.
Editor and database-tool integration
The VS Code extension activates when a .sql file opens and underlines potential problems that can be inspected by hovering. SQL Server Management Studio can use TSQLLint through its External Tools feature. These routes bring the same policy closer to editing, while the command-line interface remains the place to enforce exit-code based checks.
Pricing
| Plan | Price | What it includes |
|---|---|---|
| TSQLLint | Free | MIT-licensed software, installable with dotnet-tool, Homebrew, or NPM |
There are no paid tiers, seat charges, usage quotas, or trial terms attached to this plan. The MIT License permits use, copying, modification, distribution, sublicensing, and sale of copies subject to its conditions. That makes TSQLLint suitable for individuals and organizations that want to adopt one linting policy without subscription administration.
Platforms
TSQLLint is offered as an extension and runs on Linux, macOS, and Windows. Official installation paths are dotnet-tool, Homebrew, and NPM. VS Code provides the editor experience, while SSMS users can invoke it through External Tools. The project also documents issue and discussion navigation, but no formal support service is stated.
Who it's for
Choose TSQLLint if your work is centered on T-SQL scripts and you need rules that can distinguish advisory findings from build-breaking errors. It is particularly well suited to SQL Server developers, database administrators, and teams standardizing scripts across repositories. Teams needing a different SQL dialect, a graphical formatting-first workflow, or vendor-backed support should look elsewhere. Plugin development also presumes comfort with .NET and the net6.0 target.
Pros and cons
Pros
- Clear automation gate: error-level violations return a non-zero exit code, so command-line pipelines can enforce policy.
- Useful correction shortcut: auto-fixable findings can be changed with --fix or -x.
- Flexible policy: a .tsqllintrc file, severity choices, compatibility levels, and custom plugins support organization-specific standards.
- Broad desktop reach: Linux, macOS, and Windows support plus VS Code and SSMS integration covers common SQL Server workstations.
- No licensing cost: the free MIT-licensed plan has no published seat or quota restrictions.
Cons
- Narrow dialect coverage: it is designed for T-SQL, so mixed-dialect teams cannot use it as one common linter.
- Extension constraints: custom rules must implement the stated interface and target net6.0, limiting who can maintain plugins.
- Partial automation: only issues identified as auto-fixable are changed automatically; remaining violations need human work.
- No formal support tier: users have repository issue and discussion routes rather than a stated support offering.
Alternatives
For a wider comparison, see SQL Linters and Formatters.
- SQLCheck is another free, open-source command-line option for Linux, macOS, and Windows.
- sqlfmt is better when browser-based formatting through WebAssembly and no installation are priorities.
- Poor SQL suits readers wanting online and offline formatting with SSMS/Visual Studio plugins and command-line use.
- JSQLFormatter is an alternative free formatter for Linux, macOS, self-hosted, and Windows environments.
- SQL Enlight is the paid choice when a documented free trial and build-machine deployment are preferred.
- sqlfmt fits browser users who want a free tier with 20 analyses per day and five dialects.
- Sqruff is another free option spanning extensions, desktop systems, self-hosting, and the web.
- RegSQL is aimed at browser-local formatting with a free plan and optional AI requests.
Verdict
TSQLLint is a strong choice for SQL Server teams that want a free, scriptable T-SQL policy with configurable severities, optional fixes, and editor access. Its main reason to choose it is the combination of non-zero error enforcement and extensibility without license cost. Look elsewhere if you need multi-dialect coverage, a formatter-led product, or formal vendor support.
The verdict
TSQLLint provides configurable T-SQL checks, optional automated fixes, and integration paths for command-line and editor workflows. Its scope is T-SQL, and custom plugins must meet its stated interface and target requirements.
Questions people ask
How much does TSQLLint cost?
The TSQLLint plan is free. It is distributed under the MIT License.
Which SQL dialect does it support?
Its supported dialect is T-SQL (Transact-SQL).
Can TSQLLint fix problems automatically?
Yes. The command-line tool can fix problems identified as auto-fixable with --fix or -x.
Can I customize its rules?
Yes. Rules can be off, warning, or error, and custom .NET plugins can implement IPlugin and target net6.0.
Where can I install or use it?
Official installation methods are dotnet-tool, Homebrew, and NPM. It also has a VS Code extension and can run from SQL Server Management Studio External Tools.
What the maker publishes
- Auto-fix
- The command-line tool can fix problems it identifies as auto-fixable using the --fix or -x option. source
- Configuration
- Users can create a .tsqllintrc configuration file, and the tool uses an in-memory default configuration when none is found. source
- Install methods
- The project lists dotnet-tool, Homebrew, and NPM as officially supported installation methods. source
- Intended users
- The documented use is for people working with TSQL scripts who want to configure and report on undesirable patterns. source
- License
- The software is distributed under the MIT License, which grants permission to use, copy, modify, distribute, sublicense, and sell copies subject to its conditions. source
- Plugins
- Users can extend the tool with custom .NET plugins that implement TSQLLint's IPlugin interface and target net6.0. source
- Purpose
- TSQLLint describes, identifies, and reports anti-patterns in TSQL scripts. source
- Rule controls
- Rules can be configured as off, warning, or error; violations configured as errors return a non-zero exit code. source
- Security
- The repository lists a security policy, but its security-policy page could not be opened during this research. source
- SQL compatibility
- The configurable SQL Server compatibility levels listed are 80, 90, 100, 110, 120, 130, 140, and 150. source
- SQL placeholders
- Before applying lint rules, TSQLLint replaces SQL file placeholders with values supplied through environment variables. source
- SSMS integration
- The project says SQL Server Management Studio can use TSQLLint through its External Tools feature. source
- Support
- The repository provides issue and discussion navigation, but the opened project pages do not state a formal support offering. source
- VS Code integration
- The VS Code extension activates when a .sql file is opened and underlines potential problems for inspection by hovering. source
Checked against the maker's pages on 30 Sept 2026.