> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/languages/pl-sql.md).

# PL/SQL

PL/SQL analysis is available starting in SonarQube Server Developer edition. This page is for SonarQube Server 2026.5.

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

Discover and update the PL/SQL-specific [Analysis parameters](/sonarqube-server/analyzing-source-code/analysis-parameters.md) by going to **Administration** > **Configuration** > **General Settings** > **Languages** > **SQL**.

## Advanced parameters <a href="#advanced-parameters" id="advanced-parameters"></a>

### Default schema <a href="#default-schema" id="default-schema"></a>

|                             |                                                                                                                                                                                                                             |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Parameter**               | **Description**                                                                                                                                                                                                             |
| `sonar.plsql.defaultSchema` | <p>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.</p><p>Defaults to <code>sonar.plsql.jdbc.user</code>.</p> |

### Data dictionary <a href="#data-dictionary" id="data-dictionary"></a>

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`         | <p>JDBC user to authenticate the connection.</p><p>Will be used as the default schema name if not specified otherwise via <code>sonar.plsql.defaultSchema</code>.</p> |
| `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 <a href="#related-pages" id="related-pages"></a>

* [Adding coding rules](/sonarqube-server/extension-guide/adding-coding-rules.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/languages/pl-sql.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.