Data Dictionary is not configured warning

When I look in SonarCloud, I always have the following warning:

The Data Dictionary is not configured which prevents rule(s) S3641, S3921, S3618, S3651 to raise issues. See https://docs.sonarqube.org/display/PLUG/Data+Dictionary

However we don’t use any oracle connection, but SQL connection. How do we need to configure this to prevent this warning from coming up?

I’m not sure what you mean by:

we don’t use any oracle connection, but SQL connection.

Some possible workarounds:

  • Exclude sql files from the analysis:
    sonar.exclusions=**/*.sql
  • Remove the rules mentioned in the message from the PL/SQL quality profile which is used by your project

I mean that we don’t use Oracle databases, but only Microsoft SQL databases.

We don’t want to exclude the sql files, because there is a lot of business logic in the Stored Procedures.

Do you have any tips how to fill in these parameters for Microsoft SQL server/database
https://docs.sonarqube.org/latest/analysis/languages/plsql/

I suggest that you configure your project so that files with a “.sql” suffix are analyzed by the T-SQL analyzer instead of the PL/SQL analyzer:

sonar.tsql.file.suffixes=sql,tsql
sonar.plsql.file.suffixes=pks,pkb
1 Like