We are pleased to release version of SQL Enlight For Developers.

The most significant aspect of this update, besides some small fixes, is the command-line interface, which is now available also for the Developers edition.

We are pleased to announce the release of the new SQL Enlight edition – SQL Enlight For Build Machines

This edition is meant for continuous integration servers, build agents, or physical and virtual machines that use SQL Enlight to analyze SQL Server databases or T-SQL code, and produce analysis reports.

The Build Machines edition includes command line interface, MSBuild tasks, and Automation API.


All SQL Enlight commercial and personal licenses purchased since July 1, 2019, are eligible for a free upgrade. The upgrade includes a 1-year subscription.
If you have such licenses and you would like to upgrade, please send an upgrade request to sales at sqlenlight dot com. Please include information about your purchase or particular SQL Enlight product keys.
If your license is purchased earlier,  you can purchase a subscription renewal.

We are delighted to announce the release of the new major version of SQL Enlight.

We have prepared some compelling new features in this release:

  • In the Analysis Rule Designer, there are numerous enhancements – such as match suggestions, snippets, and simple rule expressions. See Analysis Rule Designer documentation for more details.
  • New Simple Analysis Rule type that uses XPath match expressions and can be created using a few mouse clicks.
  • Support for automatic fixing of code and database analysis issues – currently about 30 analysis rules have automatic fixes.
  • Support for creating custom fixes for code and database rules.
  • New analysis rule properties  – technical debt properties and separate ‘How to fix’ description. The new properties will be used in the reporting and will allow some other view of the analysis results.
  • The new Analysis Whitelist allows databases and objects to be excluded from the analysis results.

With the new major version of SQL Enlight, there are some changes to our licensing model:

  • We divided SQL Enlight into two editions – SQL Enlight for Developers and SQL Enlight for Build Machines.
  • We replaced the perpetual license for a major version with an update and support subscription combined with a perpetual fallback license for all the releases before the subscription end date.
  • There are also changes to the Commercial and Personal license prices.

To be able to introduce the new improvements, we had to discontinue the support for the old SQL Server Management Studio and Visual Studio versions. SQL Enlight 1.9 will continue to work with the old SQL Server Management Studio and Visual Studio versions, but new fixes and features will only be released for newer versions of SSMS and VS.

These are the SSMS and Visual Studio versions that are not supported anymore:

  • SQL Server Management Studio 16
  • SQL Server Management Studio 2014
  • SQL Server Management Studio 2012
  • SQL Server Management Studio 2008 R2
  • SQL Server Management Studio 2008
  • Visual Studio 2015
  • Visual Studio 2013
  • Visual Studio 2012
  • Visual Studio 2008
  • Visual Studio 2005


We are happy to announce the release of SQL Enlight with version

Improvements in this update:

  • Added parser support to ALTER DATABASE SCOPED CONFIGURATION statement for the new options introduced in SQL Server 2019.
  • Added parser support for new in SQL Server 2019 option – OPTIMIZE_FOR_SEQUENTIAL_KEY
  • Added parser support TOP clause with floating-point number expression such as TOP 99.99

We are happy to announce the release of SQL Enlight with version

Fixes and improvements in this update:

  • Fix issues with analyzing case-sensitive SQL Server instances and databases.
  • Fix syntax error when parsing IF/ELSE statements followed by a THROW statement or a WITH CTE clause.
  • Fix analysis rule SA0184 false positive related with TOP clause.
  • Enhanced analysis rule SA0020 with a rule parameter for ignoring temporary tables and table variables.
  • Fix some other minor issues.

We are excited to announce the release of SQL Enlight with version

What’s new in this update:

  • New analysis rule SA0271. The rule checks T-SQL statements and reports usages of any of the configured as not recommended syntax for column aliases.
  • New analysis rule  SA0272. The rule checks for SELECT statements not having neither WHERE nor JOIN clauses.

Fixes and improvements in the standard analysis rules

  • Fixed a common analysis rule problem related to CROSS/OUTER APPLY operators not taken into consideration when selecting table sources
  • Fixed false positives in analysis rules SA0124, SA0126, SA0132 related to incorrect resolution of MIN/MAX aggregate functions return type
  • Fixed SA0060 – named parameters are not considered
  • Addressed overlapping problem with analysis rules – SA0150 and SA0166
  • Fixed analysis rule SA0266 false positive related to not considering the @@trancount check

Other fixes and improvements:

  • Fixed unhandled exception while analyzing document in Visual Studio
  • Fixed parser support for named unique index set in column definition using INDEX keyword syntax
  • Fixed problem with the command-line tool, where a comma is not accepted as a list separator when passing multiple file paths
  • Fixed parsing error related to OVERRIDE token not accepted by the parser as an identifier
  • Improved performance of the filtering of active or selected analysis rules

Today we released a hotfix update of SQL Enlight with version

Issues fixed in this update:

  • Fixed a database metadata caching issue, which caused database changes not to be loaded until a restart of SSMS or Visual Studio.

We are delighted to announce the latest release of SQL Enlight with version

What’s new in this update:

Issues fixed in this update:

  • Unhandled exception in SQL Enlight ErrorList on scroll
  • Team Settings UI setting to display validation errors on Team Settings enabled or disabled.
  • Issues in EX0018 and SA0131 related with sometimes pointing to wrong line and column
  • False positives in SA0145, SEM008, SA0172, SA0121 analysis rules
  • Formatting of multipart identifier data type in a variable declaration
  • Error when parsing a query that combines a large number of union-ed statements
  • Formatting of TOP clause
  • Other minor issues found in the previous version