Version 184.108.40.2065 of SQL Enlight is already released and available for download.
Here is what’s new in this release:
- Extended query execution plan analysis support
- A new analysis rule for query execution plan analysis – EX0018
- A new external template parameter support in the command line tool and MSBuild tasks
- Small improvements and fixes
The new parameter is added to provide a way to set external analysis template which to be used during analysis instead of the default one. Check the SQL Enlight documentation for the command line tool and MSBuild tasks parameters.
As the Execution Plan Analysis is the most important feature update in this release, here we have prepared a separate post for it.
We will be happy to help you if you have any questions or comments.
The extended Execution Plan Analysis support is the most significant improvement in latest SQL Enlight release 220.127.116.115. It allows execution plans analysis to be automated and applied not only on separate statements or batches, but on all stored procedures and views in a given database.
One of the most exciting features in SQL Enlight is the ability to create your own static analysis rules. This is very powerful feature which can be of great use and unleash almost unlimited number of possibilities for the ones who consider trying it.
The current post is the first of a series of blog posts which to guide you through the creation of custom static code analysis rules with SQL Enlight. Each of the subsequent articles will cover the implementation of several interesting analysis rule and will point some unfortunately not so obvious features and abilities of SQL Enlight static code analysis engine.
The SQL Enlight analysis templates are XML files that contain analysis rules and analysis groups definitions. The templates can be imported in SQL Enlight and this way can update or add new rules to the currently supported set of rules. Read more
Obsolete SQML elements replaced in 18.104.22.1684
During the optimization of SQL Enlight, we did small changes in the SQML schema. These changes will affect only the users who have created their own custom analysis rules.
The SQML elements: pu:optional, pu:essential and pu:binding are no longer generated and are replaced by pu:semicolon and pu:dot. Read more