Hi,
Indeed, we already identified such a problem in our T-SQL parser thanks to the feedback of another user. This problem was tracked as SONARTSQL-249 and we fixed it a few months ago.
Updating SonarQube to the latest version should resolve your problem.