Release Notes - SonarTSQL - Version 1.0 - HTML format

New Feature

  • [SONARTSQL-1] - The TSQL syntax should be highlighted in SonarQube
  • [SONARTSQL-2] - Duplications should be detected based on the CPD API
  • [SONARTSQL-3] - Provide metrics for lines of code and lines of comments
  • [SONARTSQL-4] - Rule: Function and procedure names should comply with a naming convention
  • [SONARTSQL-5] - Support NOSONAR
  • [SONARTSQL-6] - Provide metrics for number of functions and statements
  • [SONARTSQL-8] - The logs should report the progress of the analysis
  • [SONARTSQL-9] - Rule: Analysis failure preventing from detecting quality flaws and bugs
  • [SONARTSQL-11] - Rule: Local variable and parameter names should comply with a naming convention
  • [SONARTSQL-12] - Rule: Identical expressions should not be used on both sides of a binary operator
  • [SONARTSQL-13] - Rule: Variables should not be self-assigned
  • [SONARTSQL-14] - Rule: All branches in a conditional structure should not have exactly the same implementation
  • [SONARTSQL-15] - Rule: Related "IF"/"ELSE IF" statements and "WHEN" clauses in a "CASE" should not have the same condition
  • [SONARTSQL-16] - Rule: "WHERE" clause conditions should not be contradictory
  • [SONARTSQL-17] - Rule: Queries that use "TOP" should have an "ORDER BY"
  • [SONARTSQL-18] - Rule: Two branches in a conditional structure should not have exactly the same implementation
  • [SONARTSQL-19] - Rule: Columns to be read with a "SELECT" statement should be clearly defined
  • [SONARTSQL-20] - Rule: "LIKE" clauses should not start with wildcard characters
  • [SONARTSQL-21] - Rule: Column names should be used in an "ORDER BY" clause
  • [SONARTSQL-22] - Rule: "DELETE" and "UPDATE" statements should contain "WHERE" clauses
  • [SONARTSQL-23] - Rule: "INSERT" statements should explicitly list the columns to be set
  • [SONARTSQL-24] - Rule: Collapsible "if" statements should be merged
  • [SONARTSQL-25] - Rule: "CASE" expressions should end with "ELSE" clauses
  • [SONARTSQL-26] - Rule: "CASE" expressions should not have too many "WHEN" clauses
  • [SONARTSQL-27] - Rule: Queries should not join too many tables
  • [SONARTSQL-28] - Rule: Lines should not be too long
  • [SONARTSQL-29] - Rule: Jump statements should not be followed by other statements
  • [SONARTSQL-30] - Rule: Track uses of "NOSONAR" comments
  • [SONARTSQL-31] - Rule: Deprecated features should not be used
  • [SONARTSQL-32] - Rule: Size should be specified for string variables
  • [SONARTSQL-34] - Rule: "NULL" should not be compared directly
  • [SONARTSQL-35] - Rule: "GOTO" statement should not be used
  • [SONARTSQL-36] - Rule: Functions and procedures should not have too many parameters
  • [SONARTSQL-37] - Rule: String literals should not be duplicated
  • [SONARTSQL-39] - Rule: Unused local variables should be removed
  • [SONARTSQL-40] - Rule: Statements should be on separate lines
  • [SONARTSQL-41] - Rule: The number of variables in a FETCH statement should match the number of columns in the cursor
  • [SONARTSQL-42] - Rule: Code should not be dynamically injected and executed
  • [SONARTSQL-43] - Rule: Constraint should validate existing data
  • [SONARTSQL-44] - Rule: "WHEN" clauses should not have too many lines of code
  • [SONARTSQL-45] - Rule: Track uses of "TODO" tags
  • [SONARTSQL-46] - Rule: Unused procedure and function parameters should be removed
  • [SONARTSQL-47] - Rule: "@@IDENTITY" should not be used
  • [SONARTSQL-48] - Rule: Triggers should not "PRINT", "SELECT", or "FETCH"
  • [SONARTSQL-51] - Rule: "CASE" input expressions should be invariant
  • [SONARTSQL-52] - Rule: Redundant pairs of parentheses should be removed
  • [SONARTSQL-53] - Rule: Column references should not have more than two-parts
  • [SONARTSQL-54] - Rule: "ANSI_NULLS", "ANSI_PADDING" and "CONCAT_NULL_YIELDS_NULL" should not be configured
  • [SONARTSQL-55] - Rule: Deprecated system tables and views should not be used
  • [SONARTSQL-57] - Protect the SonarTSQL commercial code analyzer with a standard licensing mechanism
  • [SONARTSQL-58] - Rule: Empty statements should be removed
  • [SONARTSQL-59] - Obfuscate produced artifact
  • [SONARTSQL-60] - Rule: Conditionals should start on new lines
  • [SONARTSQL-62] - Rule: Unused labels should be removed
  • [SONARTSQL-67] - Rule: Multiline blocks should be enclosed in BEGIN...END
  • [SONARTSQL-69] - Rule: Output parameters should be assigned
  • [SONARTSQL-70] - Rule: Duplicate values should not be passed as arguments

Improvement

  • [SONARTSQL-38] - S1764 should raise issues on non-consecutive operands

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.