To view a saved set of performance data:
The SQL Outline view shows all of the SQL statements that meet both of these conditions:
Example 1:
Suppose that an application contains two SQL statements, A and B. You generate performance data for those SQL statements and save that data set with the name Test.
In your application, you delete statement B, along with the code that ran it. You add statement C and code to run it. The SQL Outline view then shows statements A and C, but no longer shows the replaced statement B.
Next, you open the saved data set Test. The SQL Outline view then shows only statement A and its performance data. Statement A is the only statement that is both currently in the application and in the saved data set.
Example 2:
Suppose that an application named myApplication contains SQL statement A at line 100 in a source file. You save a set of performance data for myApplication. Then, you edit statement A, which remains at line 100 of the same source file. When you load the saved performance data set in the SQL Outline view, the view shows the original statement A nested under the edited statement A.
Example 3:
Suppose again that an application named myApplication contains SQL statement A at line 100 in a source file. You save a set of performance data for myApplication. Then, you edit the source file, causing statement A to appear at line 110. When you load the saved performance data set in the SQL Outline view, the view does not show statement A.