I’m sorry but providing a script analyzing TSQL code would be equivalent to implementing a third party application. It goes beyond what I can provide on this forum. If you have any question regarding SonarQube documentation I’ll gladly answer them.
I suggest that as a first step you create manually a file, let’s name it
report.txt, and write into it a generic report. You have an example in the doc I referenced above. Change the
textRange to match an existing code file.
sonar.externalIssuesReportPaths=report.txt in your
sonar-project.properties and run the analyzer. You should see these issues appear in SonarQube.
Once you have all this working you can implement the script generating the