One of the best features of QueryAdvisor is the Repository. This central storage compartment is used for holding all SQL commands and sorting them by structure, frequency and duration.
All session variables and entities within the Repository are sorted by chronological order.
QueryAdvisor allows you to assign the desired color to individual SQL commands which will allow you to easily identify them within the data flow.
In QueryAdvisor the processed trace files are grouped by instances. The start and end time for the respective traces are automatically determined as well as various parameters such as bind, commit, or exec.
QueryAdvisor also displays the status of each instance (i.e. whether or not it has been processed).
When you select an instance or an individual file, it is automatically marked in the Repository. In addition, the start and end times for each trace file can be displayed in a Gantt chart.
In order to allow you to execute plans, QueryAdvisor monitors all objects as well as associated access paths and frequency of occurrence.
Once you select a single object, all related SQL commands will be automatically selected in the Repository. It is also possible to perform filtering by an instance and generate a graphical representation of the results.
All execution plans for SQL commands are properly sorted and recorded separately as individual instances and sessions. This feature allows you to detect simple SQL commands with unstable execution plans.
It also allows you to detect differences between individual instances and environments.
Individual trace files can be displayed according to the individual cursors and in chronological order.The trace files are displayed depending on the release and the exact date, while the details of the selected event will be shown in the footer.
There is also wait functionality for individual events. Upon request, it’s possible to resolve the dynamic parameters P1, P2 and P3 to the underlying database.
By using the Profiler feature you can easily transfer individual SQL commands from the Repository to the profile. This will allow you to test the SQL commands against a variety of environments.
The test results are then automatically compared to the values stored in the Repository. In case there is a time excess over a predetermined period, the Outline Wizard feature automatically tests the SQL commands against different scenarios and optimizes them.
The File Viewer feature allows you to quickly locate the relevant position within the original tracefile.
In case there is an error during scanning or within the individual bind variable, the File Viewer automatically displays the exact location of the error within the tracefile.
The actual size of the displayed part of the file can be adjusted and customized.
The Wait Events for each trace file are recorded and processed by instance and type.
Individual events can be assigned custom colors allowing you to easily identify them within the data flow. It is also possible to filter the events by instance and generate the graphical representation of the results.