Examples of using Execution plan in English and their translations into Spanish
{-}
-
Colloquial
-
Official
The following sections explain how to retrieve and read an execution plan to optimize performance in various databases.
Deciding to build a specialized or generic execution plan presents a dilemma for the database.
The tools provided by IBM return the execution plan in a pretty awkward format.
Getting an execution plan from DB2 LUW is a three step procedure where the first step is a one-time setup.
can very easily show an execution plan but use very different ways to format them on the screen.
To create an execution plan, you just have to prefix the respective SQL statement with explain plan for.
Some of the columns shown in this execution plan were removed in the book for a better fit on the page.
Up till PostgreSQL 9.1, the execution plan was already created with the prepare call
This is very handy if you want to post an SQL Server execution plan on a forum or similar platform.
The execution plan is not yet the same as it was in the previous section without UPPER;
Obtaining the predicate information from a MySQL or PostgreSQL execution plan is even more awkward.
The Oracle execution plan shows the estimated memory requirement in the"Bytes" column.
the database handles it like a different statement and recreates the execution plan.
That is, you should always use bind parameters except for values that shall influence the execution plan.
In all reality, there are only a few cases in which the actual values affect the execution plan.
Prefix any SQL statement with explain plan for to store the execution plan details in the explain tables.
A short reference of the most common DB2 LUW execution plan operations.
B in the execution plan above.
Filter predicates are just labeled Predicates in SQL Server's graphical execution plan.
Bind peeking enables the optimizer to use the actual bind values of the first execution when preparing an execution plan.