By default, creating of indexes in CleverPath Reporter is set to true so that tables can be joined based on indexes which results in faster execution. However, on some databases this causes the SQLStatistics call to run on the database which can slow down processing on the database side.
This document will explain how to turn off indexing in CleverPath Reporter so that the SQLStatistics call will not run.
- Open your default.mdl file (which can be found under \config directory) in your CleverPath Reporter Administrator.
- If you have selected all available data sources you will see the dialog below. The most important one that needs to be selected is the ODBC datasource.
- Click on "Query Governor Options" tab and make sure "Save Options to Workspace" checkbox is checked.
- Click on "Configurations" tab and then click on "New" button to define a new configuration. Give this configuration a name and select ODBC as the data source. Say OK to create the new configuration.
- In the Configuration dialog, click on "Data Sources", go to "Query Governor Options" tab and check "Save Options to Workspace" checkbox. Depending on the requirement you can customize your configuration here but we do not need them at this moment.
- Now save this configuration (go to File->Save). Also install this configuration into your prorep.prf file by going to File->Install Workspace and selecting prorep.prf file in your dialog.
- Before creating a report open your default.mdl file under <CleverPath_Install_Dir>\config in an editor and make sure the flag INDEXES has a NO next to it. If you find YES manually change it to a NO. This is how my default.mdl file looks.
- Now Open your CleverPath Builder and create a new report. While selecting the source type select the newly defined configuration and you should be able to see a list of tables.
By setting INDEXES to NO we will be turning off creating indexes for the tables and hence no SQLStatistics call will be generated.
We take pride in our technical documents and are interested in your feedback.
Please email your comments to us directly at:
email@example.com Be sure to include the document id in the message.