Case Sensitive - SQL Coverage - Differentcase files ignored

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) :- * Developer Edition
    Version 9.9 (build 65466)
  • how is SonarQube deployed: zip, Docker, Helm
  • Running SonarAnalysis on SQL projects
  • Implement SQL analysis

While running the code analysis for databases, we see that SonarQube is not able to find the file for coverage if the casing of the file name is different to that of the underlying database object. Is there a way that the code analysis can be done in a case-insensitive way?

E.g., We don’t get coverage for the stored procedure [Decision].[DecisionMatchResult].
The log shows INFO: File for coverage can’t be determined [Decision].[DecisionMatchResult], was: ‘
The reason is because the underlying file is ‘Stored Procedures/decision.DecisionMatchResult.sql’ so apparently there is no filename matching for the object because of different casing used for the filename.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hey there.

Thanks for the report.

Can you tell me what OS you’re running analysis on? Linux or Windows?

Hi Colin

Its Windows machine where analysis is running.

Thanks. Indeed I would expect some case-insensitivity there.

However, I’m not sure we can say for sure that it’s a case of case-sensitivity… unless changing the file name kicks everything into place. Can you try that, just to confirm (I’m not suggesting that’s the final solution).