Inspect
After adding or modifying an Inspector in the SQL Inspector window, SQL statements and statistics from the database are retrieved by executing the Inspect function. Only one Inspector can be started at a time.
To start the inspecting process
-
Select an Inspector job.
-
Click
.
If the start time of the Inspector has not been reached, the SQL Inspector waits until it is time to begin. During and at the end of the inspecting, information is updated on the SQL Inspector window. Inspect terminates automatically once the end time is reached, except for ad-hoc inspecting. The ad-hoc inspecting process has no ending time so it must be terminated manually.
To abort the inspecting
Click 
Note: If you have already executed the Inspect function for an Inspector, re-executing the Inspect function will erase all existing information.
Ad hoc Inspect
Ad-hoc inspect allows the retrieval of the SQL performance statistics without considering or setting the scheduled start date and time.
To start an ad-hoc inspection
-
Select an Inspector job
-
Right-click and select Ad-hoc Inspect.
The process will not stop until you click
Abort Inspect
After the Inspect function has been executed from the SQL Inspector window, it can be aborted at any time.
To abort the inspecting
Click
It may take several seconds for all the events to close down.
Scan Inspector
The SQL statements collected by the Inspector can be scanned in the SQL Scanner to classify the SQL statements to help identify which SQL statements are likely to be causing performance problems.
To scan an Inspector from the SQL Inspector window:
-
Select an Inspector job.
-
Right-click and select Scan.
The selected Inspector is copied to the SQL Scanner window for scanning. If the SQL Scanner window is not opened then you will need to first select or create a job group from the Group Manager window. Once added, the scanning starts automatically.