Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
Your browser does not support iframes.

Description / Features

The Toad CodeXpert plugin is an extension of the PL/SQL plugin (commercial) and can only be used with it.


  • It scans source code from files on disk. This mode is generally used in enterprise environments with configuration management strategies (use tools like Subversion or Clearcase).
  • It connects to the database and analyzes all the objects stored in that database. This mode is NOT supported by Sonar.


  1. Install the Toad CodeXpert plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server



  • Quest Software Toad 9.5 or higher with the CodeXpert module (included into Toad for Oracle Xpert, Toad for Oracle Professional and Toad Development Suite for Oracle).
  • A connection to an Oracle database if you use Toad 9.x or 10.x. This is a limitation of Toad that needs to be connected to the database even if it is not used by the CodeXpert module. So you can set a “fake” connection to an empty database.


The following settings need properties have to be added to set (at project level through the ' PLSQL plugin specific properties (required if you use Toad)
# Those properties can also be set in $SONAR_RUNNER_HOME/conf/' file or at instance level through the '' file
# or specified through the Web interface to avoid repeating them on each PL/SQL project.or web interface):


Code Block
sonar.plsql.toad.exePath=C:/Program Files/Quest Software/Toad for Oracle 10.5/Toad.exe






Running an a

Activate some rules from Toad CodeXpert in your project quality profile and run a Sonar analysis.

Sonar automatically configures and launches Toad CodeXpert to analyse the PL/SQL codecheck your code against the Toad CodeXpert's rules.


Toad Code Xpert CodeXpert 9.x is unable to start from the command-line when the month of the current date contains an accent ("Décembre" in French for example). The workaround for this is to change the regional settings on the machine.


JIRA Issues
titleRelease 1.0