SA0002 : Variable declared but never referenced or assigned

Declaring variables without subsequent use or assignment can clutter the code and lead to confusion. This issue often arises during rapid development or refactoring, where variables may be declared in anticipation of use but ultimately remain unused. Unused variables can make the code harder to read and increase the cognitive load for developers trying to understand the flow and logic.

Example of problematic query with unused variable:

1DECLARE @UnusedVariable INT;
2SELECT * FROM Employees;

In this example, the variable @UnusedVariable is declared but never used in the SQL script. This is an issue because:

• Unused variables can give the false impression that they play a role in the logic, misleading developers or reviewers.

• They contribute to code bloat, which can make maintenance and debugging more challenging.

Remove unused variable declarations from your SQL scripts to improve code quality and maintainability.

Follow these steps to address the issue:

1. Identify any variables that are declared but not used in your script. Look for statements like DECLARE @VariableName DataType; where the variable @VariableName is not subsequently referenced.

2. Remove the declaration of the unused variable to clean up the code. Ensure that any logic dependent on the variable is not affected (if originally anticipated for use).

3. Review your script to confirm that the removal of the unused variable does not impact the functionality of the remaining SQL statements. Look for any comments or planned sections that anticipated variable use and update them if necessary.

Example of corrected query without unused variable:

1-- Removed 'DECLARE @UnusedVariable INT;'
2SELECT * FROM Employees;

The rule has a Batch scope and is applied only on the SQL script.

The rule does not need Analysis Context or SQL Connection.

Design Rules, Code Smells

There is no additional info for this rule.

Other Resources