Questions tagged [execution-plan]

The strategy selected by the query optimizer to process a query.

SQL is a declarative language and does not specify the actual algorithm used to resolve a query. The query plan generator can generate a number of semantically equivalent approaches to resolving a query and select the one that it estimates to be most efficient based on a heuristic.

Various transformations can be applied to a query plan for example, the order in which tables are joined or predicates applied can be changed, various join algorithms such as hash, merge or nested loops joins can be used, or internal results can be calculated and materialised for later use.

A sub-optimal plan can result in poor query performance. Most database management systems supply tools for analysing query plans and examining the query plan is a key technique for tuning a query.

1182 questions
1
vote
1 answer

SentryOne Plan Explorer properties window

Does the SentryOne Plan Explorer have a properties window similar to SSMS. I see the tool tip window next to the operators in the execution plan but no properties option ?
vir
  • 41
  • 2
0
votes
1 answer

Comparing execution plans

How does the optimizer compare different execution plans of the same query? Let's say we have two complex and structurally different execution plans, how can I know if they are providing the same result?
maya-bf
  • 3
  • 1
0
votes
2 answers

Non Clustered Index Scan Properties window - Predicate order different than query order

SQL 2012 Data Warehouse type environment... I have a Non Clustered Index on a Type 2 Dimension table, which I'll just call DimStudent. The index is defined as below, with data types and other info in parentheses for context: ( [StudentID] ASC…
John G Hohengarten
  • 663
  • 1
  • 6
  • 18