Indicates whether the plan baseline is accepted ({@code YES}) or not ({@code NO}).
Indicates whether a plan that is automatically captured by SQL plan management is marked adaptive or not.
When a new adaptive plan is found for a SQL statement that has an existing SQL plan baseline, that new plan will be added to the SQL plan baseline as an unaccepted plan, and the {@code ADAPTIVE} property will be marked {@code YES}. When this new plan is verified (either manually or via the auto evolve task), the plan will be test executed and the final plan determined at execution will become an accepted plan if its performance is better than the existing plan baseline. At this point, the value of the {@code ADAPTIVE} property is set to {@code NO} since the plan is no longer adaptive, but resolved.
Indicates whether the plan baseline is auto-purged ({@code YES}) or not ({@code NO}).
Indicates whether the plan baseline is enabled ({@code YES}) or disabled ({@code NO}).
Indicates whether the plan baseline is fixed ({@code YES}) or not ({@code NO}).
The origin of the SQL plan baseline.
The unique plan identifier.
Indicates whether the optimizer was able to reproduce the plan ({@code YES}) or not ({@code NO}). The value is set to {@code YES} when a plan is initially added to the plan baseline.
The unique SQL identifier.
The SQL text (truncated to the first 50 characters).
The date and time when the plan baseline was created.
The date and time when the plan baseline was last executed.
*Note:** For performance reasons, database does not update this value immediately after each execution of the plan baseline. Therefore, the plan baseline may have been executed more recently than this value indicates.
The date and time when the plan baseline was last modified.
The summary of a SQL plan baseline.