Why is this an issue?
Shared naming conventions allow teams to collaborate effectively. This rule raises an issue when a local variable or function parameter name does
not match the provided regular expression.
Noncompliant code example
With the default regular expression @[a-zA-Z0-9_]*
:
CREATE PROCEDURE proc1
@@var1 INT -- Noncompliant
AS
BEGIN
DECLARE @@var2 INT; -- Noncompliant
END