SQL Enlight Code Quality extension for Azure DevOps consists of build task can be added to the build definition. The task analyses T-SQL code against best practices and its output can be easily combined with the build test results.

The build task uses more than 230 standard analysis rules, which to ensure code quality, detect potential defects, and check against best practices.
SQL Enlight supports the creation of custom rules, which can be also used by the Azure DevOps extension.

The SQL Enlight Code Quality extension is now in preview and is available for install in Visual Studio Marketplace.

The SQL Enlight Code Analysis Task works together with the Publish Test Results task in order to combine code analysis results with the Test Results.

1. Find and add SQL Enlight Code Analysis build task.

1. Add the Publish Test Results task after the SQL Enlight build task

All the SQL Enlight Code Analysis settings are optional and are grouped into two categories – General and Advanced.

Include Pattern
Optional regex pattern for matching.SQL files, which to be analyzed. The pattern can be used to limit the analyzed files to a specific folder.

• If provided only the files having path matching the regex pattern will be analyzed.
• If not provided, all files will be included by default.

Exclude Pattern
Optional regex pattern for matching.SQL files, which to be excluded during the analysis. The pattern can be used to exclude specific folders or files from the analysis.

• If provided only the files having path not matching the regex pattern will be analyzed.
• If not provided, there will not be any excluded files.

Include Rules
Optional comma-separated list of rules or analysis groups which to be enabled during the analysis.
By default, all active rules will be included.

Exclude Rules
Optional comma-separated list of rules or analysis groups which to be disabled during the analysis.
By default, there won’t be any excluded rules.

Fail On Violation
The setting controls the build outcome in case any rule violations are found. It can be used to fail the build in case any analysis rule is violated.

• If enabled, the task will fail if any rule violation is found.
• If disabled, the violations will be added to test results, but the build won’t be forced to fail.

Analysis Context
Optional analysis context file.

Connection String
An optional SQL connection string, which to be used for loading analysis context.

Report Output
Optional output file for the generated report.

Custom Properties
Optional custom properties, which to be provided to the generated report.

Analysis Template
An optional analysis template file, which to be used for the analysis.