10.1 | Analyzing source code | Languages | PL/SQL
PL/SQL
On this page
PL/SQL analysis is available starting in Developer Edition.
Language-specific Properties
Discover and update the PL/SQL-specific properties in Administration > General Settings > Languages > PL/SQL.
Advanced parameters
Default schema
| Parameter | Description |
sonar.plsql.defaultSchema | When a schema object (table, view, index, synonym) is referenced in SQL code without a schema prefix, the analyzer will assume that it belongs to this schema. |
Data dictionary
Some rules raise issues only when a data dictionary is provided during analysis. To provide a data dictionary, you must define the following properties in the sonar-project.properties file or on the scanner command line using the -D prefix:
| Parameter | Description |
sonar.plsql.jdbc.url | URL of the JDBC connection. Required for data dictionary lookup. For example: jdbc:oracle:thin:@my-oracle-server:1521/my-db |
sonar.plsql.jdbc.user | JDBC user to authenticate the connection. |
sonar.plsql.jdbc.password | JDBC password provided to authenticate the connection. |
sonar.plsql.jdbc.driver.path | Path or URL of the Oracle JDBC driver JAR. |
sonar.plsql.jdbc.driver.class | Java class name of the Oracle Driver. For example: oracle.jdbc.OracleDriver |
Providing this configuration allows SonarPLSQL to query data dictionary views such as SYS.ALL_TAB_COLUMNS in order to better analyze your SQL.
Related pages
Was this page helpful?
© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARLINT, SONARQUBE, SONARCLOUD, and CLEAN AS YOU CODE are trademarks of SonarSource SA.
