Databases Reference
In-Depth Information
Performance
To see the SQL that gets executed when a user accesses an interactive report, you can run the page in
debug mode. To do this, you must be logged on as a developer and debugging must be enabled for the
application (Edit Application, Properties region). Once you have your filter and formatting in place, you
turn debugging on by clicking the Debug button in the Developer Toolbar at the bottom on your
browser (see Figure 13-41).
Figure 13-41
. Developer Toolbar
You can then click View Debug and select the most recent record associated with the application
and page you are working on. That will display the debug output, as shown in Figure 13-42.
Figure 13-42
. Debug output
With that output, run the query in SQL Developer to analyze the performance. If you need to figure
out the bind variable values, you can look at the following APEX views:
APEX APPLICATION PAGE IR RPT
identifies user-level report settings.
•
APEX APPLICATION PAGE IR COMP
identifies computations defined.
•
APEX APPLICATION PAGE IR COND
identifies filters and highlights defined.
•
APEX APPLICATION PAGE IR GRPBY
identifies group by defined.
•
If a query is not performant in SQL Developer, it is not going to speed up when you create an
interactive report based upon that query. We often have someone complain that Application Express is
slow when it is really their SQL that is slow.
