Page History
...
After a statement is explained, the explain results are stored in the PMDB. This information includes the objects referenced by the statement and the operations performed on these objects. The top statements are automatically explained every day. You can control how many statements to explain using a setting for the Explain Statements PMDB process in AdminPoint. For more information, see the see the Precise Administration Guide.
Statements are also parsed by a proprietary Precise for Oracle parser. Parsing allows Precise for Oracle for example to highlight statement objects from the execution plan and to format execution plans. The number of statements that are parsed is again governed by a setting in the PMDB. For more information, see the Precise Administration Guide.
...
There can be statements with many execution plans. Only the latest 7 plans appear on the tree. Click More..., if available, to view additional execution plans. See “About About the Dashboard tab” on page 43, “About tab, About the Current tab” on page 51tab, "About the Activity tab” on page 61tab, and “About About the Objects tab” on page 87tab.
| Anchor | ||||
|---|---|---|---|---|
|
...
- When you edit a statement and save an alternative. See “Editing Editing an existing statement” on page 154statement.
- When you click New Alternatives in the Related SQL view, and Precise for Oracle creates an alternative SQL for you. See “Generating new alternatives” on page 156 Generating new alternatives.
- When an index recommendation is made in the What-If tab and you click Compare to switch to the SQL tab, in which case a copy of the statement is saved along with its new virtual index and execution plan. See “About the What-If tab” on page 159.
...
- Click Actions>New.
- In the New Statement dialog box, choose the relevant properties for the new statement from the drop-down lists and fill in the fields, as follows:
- Instance. Indicates the name of the instance that the statement belongs to.
- User. Indicates the Oracle user name that will parse the statement.
- Cabinet. Indicates the name of the cabinet that the statement is saved in.
- Folder. Indicates the name of the folder that the statement is saved in.
- Statement. Indicates the user-defined name of the statement.
- Comment. Provides an optional tuning comment that is to be associated with the statement.
- Text. Indicates the SQL text for the statement.
The maximum number of items displayed in the Cabinet, Folder, and Statement lists is limited. You may also type the names.
- In the Text field, enter the text for the statement.
- In the Comment field, type a tuning comment that is associated with the statement, if required.
- Click OK. The new statement is saved in the PMDB in the cabinet and folder hierarchy.
| Anchor | ||||
|---|---|---|---|---|
|
The Edit Text option lets you edit a statement that was saved in the PMDB through the New option. Collected and imported statements cannot be edited. However, you can use the Edit dialog box to save a related SQL statement and then edit the related SQL statement.
...
To re-explain a statement, in the Plan or All Plans view, click Actions>Re-Explain.
| Anchor | ||||
|---|---|---|---|---|
|
The Generate Alternatives option instructs Precise for Oracle to run the alternative SQL generator to see if it can find ways of re-writing the SQL so that the Oracle Optimizer comes up with a more efficient execution plan. It performs various mathematical transformations to the SQL, such as replacing EXISTS with IN, OR with UNION, but still so as to give an equivalent result set. The alternatives are saved in the same folder as the original and can be viewed in the Related SQL view.
...