SEAS2009 Query Optimization Final

SEAS09
SQL Server
Enterprise Architect
Summit
June 09-12, 2009
Shanghai, China
Query Optimization and
Query Tuning in SQL
Server 2008
Howard Yin
Principal Program Manager
SQL Server Customer Advisory Team
Microsoft Corp.
SEAS09
Agenda
• SQLCAT Introduction
• Query Optimizer Architecture
• Query Plan Analysis
• Influencing Plan Selection
• Special Considerations
– Parameterized Queries
– Temporary Tables and Table Variables
– Parallel Queries
• References
3
| SQL Server Customer Advisory Team
SEAS09
Agenda
• Statistics Used by Optimizer
• Parameterized Queries
• References
4
SEAS09
SQLCAT Introduction
• SQL Server Customer Advisory Team
– Part of SQL Server development group
• SQLCAT Mission
– Making customer successful
• Engage with the largest and most challenging SQL
deployments in the world, provide architectural
guidance and reviews, with direct access to product
development engineers
– Improve the product
• Through lessons learned, drive new features into the
product, share field experience with product team,
and participate in product planning
– Improve the community
• Presentation at SQL PASS, TechEd, TechReady and
many internal and external events
• Whitepapers, Technical white papers and Blogs based
on lesson learned are published at SQLCAT website:
www.sqlcat.com
• Lesson learned based training event: 5
SEAS – SQL Server Enterprise Architect
SEAS09
SQLCAT Profile
• SQLCAT structure
– Customer Advisory Team including SQL BP
 international and technology SQL

Customer
Team
excellence team ISV
– ISV team SQL

CAT
– Best practice team

• Small team with worldwide coverage
– Senior database architects with many
years of SQL Server and other RDBMS
experience
– Extensive customer, project management
experience
– Mixed consulting services, product
|
development background
6
SEAS09
SQL Server Design-win

Program
• Identify the most challenging, unique, interesting and
innovative applications running on the Microsoft
database platform
• Invest in Large Scale, referenceable SQL Server
projects across the world
– SQLCAT technical & project experience
– Design & architecture review covering performance,
operation, scalability, availability and many aspects
– Priority use of customer lab environment
• Use customer experiences to make a better product
• Share the knowledge learned from these challenging
implementations to help the world wide SQL
community.
• Reference the customer and make them a case story
7
SEAS09
Engaging SQLCAT
• Engagement through Design-win program
• Coverage/Contacts in your region
– US & worldwide:
• Lubor Kollar – lubor.kollar@microsoft.com
– Latin America
• Stuart Ozer – stuarto@microsoft.com
– Asia
• Howard Yin (GCR & Japan) – howard.yin@microsoft.com
• Peter Carlin (Taiwan & Japan) – peterca@microsoft.com
• Prem Mehra (India & US) – premm@microsoft.com
• Nicholas Dritsas (APAC) – ndritsas@microsoft.com
– Europe
• Thomas Kejser – tkejser@microsoft.com
• Alexei Khalyako – alexeik@microsoft.com
– US
• Michael Thomassy – micht@microsoft.com
• Kevin Cox – kevincox@microsoft.com
8
SEAS09
Agenda
• References
9
SEAS09
SQL Server Relational Server

High-Level Architecture
Language Processing (Parse/Bind/View Expansion)
Backup / Restore, BCP, …)

Utilities (DBCC,
Query Optimization Statement/Batch
(Plan Generation, Index Execution
Metadata, Type system,
Selection, Join Ordering,

Statistics, Costing) Query Execution
Expression Services
(Query Operators,
Plan Cache Management Memory Grants,
Parallelism)
Storage Engine (Access Methods, Database Page
Cache, Locking, Transactions, …)
SQL-OS (Schedulers, Buffer Pool, Memory
Management, Synchronization Primitives, …)
SQL Relat ional Server
Microsoft Confidential 10
SEAS09

High-Level Architecture

Utilities (DBCC,
Execution
(Plan Generation, Index

Query Execution
Expression Services
Statistics, Costing) (Query Operators,

Parallelism)
SQL-OS (Schedulers, Buffer Pool, Memory
SEAS09

This Talk – Query Optimization

Que r y Op t im iza t ion

Utilities (DBCC,
( Pla n Ge ne r a t ion ,
(Plan Generation, Index Execution

Statistics, Costing) Query Execution
Expression Services
Ind e x Se le ct ion, Join (Query Operators,

Parallelism)
Or d e r in g , St a t ist ics,
Cost in g ) SQL-OS (Schedulers, Buffer Pool, Memory
SEAS09
Query Optimization
• Query Optimization is cost based in
SQL Server
• Input to Query Optimization is
Operator Tree produced by
– Parsing SQL statement (Syntax)
– Semantic analysis and checking (aka
Algebrizing – this includes type
derivation, type checking, binding
variables, table and column names,
etc.)
• Output is Query Plan
SEAS09
Query Optimization
Select *
From …
parse/bind
Query
Hash join
opt im izer
lGenerate … Concat
Join
alternatives
… Union l … … …
lEstimate cost
… … … Output
Input
Metadata Physical
lIndices Properties
lStatistics lMemory
lConstraints lNumber of
lUser cores

SEAS09
Relational Expressions
• SQL is the standard front-end
language
• Query processing is based on
relational operator trees
»
• Query block
SELECT SUM(T.a) GroupBy T.c, sum(T.a) GroupBy T.c, sum(T.a)
FROM T, R
Filter (T.b=R.b and R.c = 5) Join (T.b=R.b)
WHERE T.b = R.b
AND R.c = 5 Cross product T Filter (R.c = 5)
GROUP BY T.c
T R R

SEAS09
Tree Transformations
Filter (A.x = 5) GroupBy A.x, sum(A.y)
Join Join Join
A B A B A B
Join Join Hash-Join
Filter (A.x = 5) B GroupBy A.x, sum(A.y) B A B
A A
Simplification Exploration Implementation

SEAS09
Sets Of Transformations
• Join reordering • Star and Snowflake

• Outerjoins queries
• Subqueries • Join elimination
• Aggregation • Indexed views
• Union • Update plans
• Index plans • Constraint checking
• Large IN lists • Parallel plans
• Empty table • Remote queries
simplification • Partitioned tables
• Bitmap filters • …

SEAS09
Costing
• Based on
– Estimated intermediate and final result
size
– Detailed model of execution algorithm
(I/O, number of CPUs, memory)
• Estimation of result size
– Histograms on distribution of values
for base table columns (table
statistics)
– Derived on each operation, e.g. filter,
join
SEAS09
Multi-Stage Optimization
• Stages
– No-choice queries (trivial plan)
– Transaction processing queries (Phase
0)
– Complex query I (Phase 1)
– Complex query II (Phase 2)
• Parameters of a stage
– Entry condition
– Transformations allowed
– Termination condition

SEAS09
SQL Server Cost-based Query

Optimization Process
Cost -based opt im izat ion
sim plify
T0 T1 Pool of alt ernat ives
(input )
search(0) search(1) search(2)

use sim plificat ion
t ransform at ions
use explorat ion and

im plem ent at ion
t ransform at ions, cost
alt ernat ives T2
(out put )

SEAS09
Optimization Phases
• Goal: don’t overspend on optimization
– E.g. don’t spend additional 1 second of optimization
time to shave off 0.5 second of run time
• Phase 1 is not entered if Phase 0 finds a plan with
cost<0.2
• Phase 2 is not entered if Phase 1 finds a plan with
cost<1.0
• Each additional phase has richer transformations and
considers additional plan types
– In Phase 0 only NL and Hash joins
– In Phase 1 initially only non-parallel plans are
considered; if the best plan so far found has cost
>=5, Phase 1 is repeated to find a parallel plan and
the “cheaper” of the parallel and non-parallel
versions will advance to Phase 2
– Phase 2 is performing for example Outer Join
reordering, Index View matching and Star Query
optimization
• | Optimization may end up in “time-out” and the best so
far (if any!) plan is sent for execution
SEAS09
IBM DB2 On NT And UNIX

Query rew rit e
heurist ically change blocks Cost -based opt im izat ion
sim plify
T0 T1 Pool of alt ernat ives
(input
bot t om -up join enum erat ion
)
search(0) search(1) search(2)
knobs t o lim it search
lNon-uniform query represent at ion

lCost -based opt im izat ion focused on join T2
ØDoes not cross “ query block boundary” (out put )
SEAS09
Oracle Architecture
• Old “rule-based optimizer”
– Use heuristics, and follow SQL syntax
– No cost-estimation considered
• New cost-based optimizer
– Follow IBM’s (old, System-R kind of
approach)

SEAS09
SQL Server - Optimizer

Extensibility
Goal: Support high paced innovation (typical

for MS products)
• Easy way to add new operators
– Logical operators, or execution algorithms
– Cardinality and cost estimation functions
• Adding new tree transformations
– Handle new operators
– Add new reordering alternatives
• Apply cost-based optimization uniformly on
all operations, beyond joins/SQL query
block
SEAS09
Tools to monitor optimization

• SQL Server 2008 has tools to see “inside”
the optimization
• Showplan contains for example
(will be covered in depth next)
– Operator cost and subtree cost
– Cardinalities of all operators (estimated
number of rows returned by the operator)
– Optimizer warnings (e.g. missing join
predicate)
– Values of variables used for optimization
• SQL Trace
• DMV sys.dm_exec_query_optimizer_info
• Perfmon counters in SQL Server: SQL
| Statistics
25
SEAS09
Agenda
• References
26
SEAS09
What affects optimizer

choices?
• Optimizer Statistics
• Indexes and constraints
• Memory
• Logical number of processors
27
SEAS09
Optimizer Statistics
• Used for costing
– Histogram
• Captures distribution of values for a column
• Max number of steps = 200
• Used for estimating cardinality of search predicates
• Single-column only
– Density
• Number of occurrences of each unique value in a
column
• Used for estimating cardinality of search predicates,
joins, agg
– String index (statistics) – new in SQL Server 2005
• Viewing statistics
– DBCC SHOW_STATISTICS
• CREATE / UPDATE STATISTICS
– Can specify FULL SCAN or sample size or sample %
– Default sample size increases logarithmically with the
number of rows
– Sp_createstats, sp_updatestats
• By default SQL Server creates and maintains statistics
automatically – the Best Practice is to use the
| default Microsoft Confidential
28
SEAS09
Auto Statistics
• Database options
– AUTO_CREATE_STATISTICS
• Stats on columns created when a query needs
them
– AUTO_UPDATE_STATISTICS – when?
• Permanent tables: 500; 500 + 20% * rows in table
when compiled
• Temp tables: 6; 500; 500 + 20% * rows in table
when compiled
• See
http://www.microsoft.com/technet/prodtechnol/sql/20
for more details
– Beware AUTO UPDATE uses default sampling
even if created as FULLSCAN => consequence
CREATE INDEX creates statistics with FULLSCAN
but subsequent auto update for the same index
will use sampling
– No auto-create or auto-update stats for table
variables (and you cannot create statistics
either)
• sp_autostats
– Display, change auto-stats setting (ON/OFF)
– Can disable auto-stats per index, table
SEAS09
Statistics Issues
… and Best Practices
• Statistics are used to derive Cardinality Estimate (CE) on each
query operation
– Filter, Join, GroupBy, …
– Warning column in showplan if missing statistics
• Limitations
– CE gets progressively less reliable across multiple joins and group-
by’s
– Hidden correlations tough to handle
• Data-level correlation: Two columns that are correlated
• Predicate-level correlation: Multiple predicates that are not
independent
– Data skew impacts estimates, especially with sampled statistics
• Hard to correctly guess density from sample
• Recompilation if number of changes to a column exceeds
thresholds
• (Re)Compilations requiring a statistic stall if auto_update stats is
executing
– Consider AUTO_UPDATE_STATISTICS_ASYNC Database option
• Best practices
– Reasons to turn off AUTO_UPDATE on a statistic
• If it is causing unnecessary recompilation - lots of updates but
they don’t change nature/distribution of data
• For increased predictability during work-day if can be scheduled
during off time
| –SQLSometimes, FULLSCAN
Server Customer Advisory Team stats
Microsoft necessary – schedule periodic update
Confidential 30
stats
SEAS09
Upgrade Considerations
• Upgrade from SS 2000
– All SS 2000 stats are considered
automatically “stale” => autostats will
take care of the “upgrade”
– Best Practice is to update statistics
manually as a part of the upgrade step
– If stats are maintained manually they all
should be manually updated during
upgrade
• sp_updatestats @resample =
'resample‘
– Details of changes are described in
http://www.microsoft.com/technet/prodtechnol
• Upgrade from SS 2005
– No need to update statistics

SEAS09
Agenda
• References
32
SEAS09
Query Plan aka Showplan

• 3 forms: textual, XML , graphical
• By contents: operators only, with cost and
cardinality estimates and with runtime
information Text XML Graphical
• Operators SET SHOWPLAN_TEXT N/A N/A
ON
• Operators and SET SHOWPLAN_ALL SET Display Estimated
estimated costs ON SHOWPLAN_XML Execution Plan in
• and card. ON Management Studio
• Run time info SET STATISTICS SET STATISTICS Include Actual

PROFILE ON XML ON Execution Plan in
• Management Studio
•
•
• SQL Trace has 8 different Showplan events in
|
Performance event category
33
SEAS09
Demo – Showplan in SSMS

• Estimated Query Plan
– Properties of the Index Seek
– Estimated # of rows, # of executions
• Actual Query Plan
– Watch for “Actual” number of rows,
estimated number of rows, number
of executions
• SHOWPLAN_TEXT, ALL, XML
• Saving and sharing the query plans

| –
34
SEAS09
Actual Query Plan
35
SEAS09
Demo – Trivial Plan in SSMS

• Trivial plan
– By investigating the syntax and
metadata optimizer knows “there are
no choices”
– Optimization Level = Trivial
• Non-trivial plan
– Optimization Level = FULL
– if early termination happens
• Reason For Early Termination has a value
– Good Enough Plan Found OR
– Timeout OR
– Memory Limit Exceeded
| –
36
SEAS09
Using DMV
• sys.dm_exec_query_optimizer_info
captures aggregate counters of
various compile time events, for
example
– How many compilations happened so
far?
– How many finished in which phase
(0,1,2,3) of optimization?
– How many Inserts, Deletes, Updates?
– Etc.
37
 | SQL Server Customer Advisory Team
SEAS09
Demo - Optimizer Warnings

• SHOWPLAN shows warnings
• Missing Column Statistics
• Missing Join Predicate
• SQL Trace events
– Errors and Warnings Event Category
• Missing Column Statistics
• Missing Join Predicate
38
SEAS09
Demo – Database Tuning

Advisor (DTA)
• Input batch file or SQL trace file or table
• GUI interface surfaces only a subset of
capabilities of the DTA engine
– Command line version is using XML
document conforming to
DTASchema.xsd
– SQL Server schemas are published at
http://schemas.microsoft.com/sqlserver
/
• Recommended use for smaller sets of
queries (as was the demo) 39
SEAS09
Missing Indexes
• In some cases the Optimizer will record
information about “missing index” in
Showplan and in several DMVs
– sys.dm_db_missing_index_groups
– sys.dm_db_missing_index_group_stats
– sys.dm_db_missing_index_details
– sys.dm_db_missing_index_columns
• The information is opportunistic and not
exhaustive

40
SEAS09
Query Plan Debugging – best

practices
• Collect “Actual Execution Plan”
• Compare “Estimated” and “Actual” row counts
– Large discrepancies indicate potential problem
spots
• Watch for Execution Warnings – BOL describes
remedies for each case
– Sort Warning
• sort operations do not fit into memory
– Exchange Spill
• buffers in a parallel query plan have been
temporarily written to the tempdb database
– Hash Warning
• hash recursion or cessation of hashing (hash
bailout) has occurred during a hashing
operation
|
–SQLBitmap Warning
Server Customer Advisory Team
41
SEAS09
Agenda
• References
42
SEAS09
Hints
• Types of Query hints
– Locking (PAGLOCK, ROWLOCK, NOLOCK,
HOLDLOCK…)
– Isolation Level (REPEATABLEREAD,
SERIALIZABLE ,…)
– Other (KEEPIDENTITY, KEEPDEFAULTS,
NOWAIT, NOEXPAND,…)
– Optimizer
• Table access
• Join
• Query
SEAS09
Optimizer Hint Classification

SELECT ProductName, Products.ProductID TABLE
access
FROM HINT
dbo.[Order Details] WITH (INDEX(0))
 INNER LOOP JOIN
dbo.Products JOIN HINT
ON [Order Details].ProductID = Products.ProductID

WHERE Products.UnitPrice > 100
OPTION (RECOMPILE, LOOP JOIN)
QUERY
HINT
44
SEAS09
Optimizer Hint Examples

• Table access hint: INDEX (n) | (name)
– Cannot force seek versus scan until 2008
• Join order, method
– FORCE ORDER query hint
• But cannot specify order across sub-queries, or
push aggregations below joins – always QUERY
level
– LOOP | MERGE | HASH JOIN – both at the query
level and individual join
• Aggregation
– HASH GROUP => Hash Aggregation
– ORDER GROUP => Stream Aggregation
• For more details see BOL
– TABLE HINT section for Table access hints
– Join Hints section for Join hints
– OPTION clause section for Query hints
SEAS09
Hints - New in 2005 and 2008

• RECOMPILE hint for individual queries
• The following hints provide more control to
“fix” the plan
– OPTIMIZE FOR hint to force particular values
of parameters to be used by the optimizer
– USE PLAN to enforce particular query plan
– PARAMETERIZATION hint
• Database level
• Inside a Plan Guide
– Plan Guides
• FORCESEEK – new table access hint in SQL
Server 2008
SEAS09
Recompile Hint
• In SS 2000: CREATE PROCEDURE WITH
RECOMPILE
• In SS 2005 and 2008, an individual
statement may have OPTION
(RECOMPILE)
– Better alternative to dynamic SQL when
forcing recompilation for each new set
of variables was suggested in Shiloh
– Easier syntax
– No need to grant access to all
referenced objects; execute on the sp
suffices
SEAS09
Optimize For Hint

OPTION ( OPTIMIZE FOR

( @variable_name = literal_constant [ ,
…n ] ) )

• Values are used only for the

optimization, not for execution
• Counteracts parameter detection – may
achieve more predictable behavior
• Cannot be used without data
knowledge Microsoft Confidential 48
SEAS09
Use Plan Hint

• Plan Stability Feature
• Idea: Use a captured XML Showplan
in a USE PLAN query hint to guide
the optimizer to choose the same
plan
SEAS09
Plan Forcing
 Usage: Query

 SELECT * FROM t
 OPTION (
 USE PLAN N‘<ShowPlanXML> …
</ShowPlanXML>’
 )

Query Hint
String literal
of XML Showplan
SEAS0
9
What’s Forced by Plan Hint

• Plan topology and order of evaluation
• Execution algorithms
• Index solutions
• Objects referenced in the query
•
 Plan Forcing is used to force cost
based decisions.
| SQL Server Customer Advisory
Team
SEAS0
9
Plan Hint Limitations

• No INSERT/UPDATE/DELETE in 2005,
YES in 2008
• No Distributed Query
• No Full-text queries
• Static, Fast_Forward cursors only
•
•
Team
SEAS0
9
Plan Guides - Idea

Out-of-band query hinting
Scenario: query is known but cannot be
modified directly in the source code yet

some hinting is desirable
Replace the Original Query by the hinted
version using “Plan Guide” system table

Original Query

Hinted Version
SELECT … SELECT … OPTION (…)
UPDATE … UPDATE … OPTION (…)
Team
SEAS0
Plan Guides Feature 9
Overview
• Create: sp_create_plan_guide
• Drop/Enable/Disable:
sp_control_plan_guide
• Matching:
– During module (SP, DML trigger, multi-
statement TVF, scalar UDF)
compilation
– During batch compilation
– Targets
• original user query
• Simple- or Force-parameterized query
 Microsoft Confidential 54
Team
SEAS0
Scenarios (all pertain to an app

9
you can’t change)

• Force use of a MERGE JOIN operation for a
specific query in a user-submitted batch
• Force optimizer to always use “worst case”
parameter value
• Force compilation sharing for queries with a
format that is the same except constant
literals are different
– Specify FORCED PARAMETERIZATION in plan
guide
• For use of a specific plan for a manually
parameterized query
Team
SEAS09
New around plan guides in

2008
• Plan Freezing - ability to create a plan from the
plan cache directly
– The plan guide is automatically created by
invoking sp_create_plan_guide_from_cache
• See documentation for the sp for boilerplate
code
• sys.fn_validate_plan_guide function validates if
the plan guide is still valid (after e.g. some
metadata changes)
• SQL Profiler trace events
"Plan_guide_successful" and
"Plan_guide_unsuccessful" are located under
the "Performance" category
• Perfmon counters "Guided Plan Executions/sec"
and "Misguided Plan Executions/sec“ provide
| similar function Microsoft as the
trace events above 56
Confidential
SEAS09
Agenda
• References
57
SEAS09
Parameterization
• In SQL Server 2000 “auto parameterization” is
used only for very simple queries
– Referred to as SIMPLE parameterization in SS
2005
• Discoverable by investigating the plan;
“parameter” is suddenly there. For example

Query: select * from T where c=5

Plan: |--Table Scan(OBJECT:([tst1].[dbo].[T]), WHERE:
([T].[C]=Convert([@1])))

• Advantage: no need to recompile for the

same query with different value instead of
“5”
SEAS09
Parameterization (contd.)
• In SQL Server 2005 “parameterization”
may be forced on a database level for
ALL queries
– Set PARAMETERIZATION option to
FORCED in ALTER DATABASE stmt
• Use only when you are sure compilation
is the bottleneck
• Some queries may get worse plans if
forcefully parameterized
• Works only against databases in 90 and
higher compatibility level
SEAS09
Parameterization (Example)
Query: select * from T where c=1 or c=2
Plan: |--Table Scan(OBJECT:([tt].[dbo].[T]), WHERE:([tt].[dbo].[T].
[c]=(1) OR [tt].[dbo].[T].[c]=(2)))

 ALTER DATABASE <dbname> SET

PARAMETERIZATION FORCED

 Plan: |--Table Scan(OBJECT:([tt].[dbo].[T]), WHERE:([tt].[dbo].

[T].[c]=[@0] OR [tt].[dbo].[T].[c]=[@1]))
 ALTER DATABASE <dbname> SET
PARAMETERIZATION SIMPLE
SEAS09
Agenda
• References
61
SEAS09
Optimizer References
• Tips, Tricks, and Advice from the SQL
Server Query Processing Team
http://blogs.msdn.com/sqlqueryprocessing
• Query Tuning Recommendations

http://technet.microsoft.com/en-us/library
• Data Warehouse Query Performance

http://technet.microsoft.com/en-us/magaz
62
Some showplan references
• Find Top N costly query plans in adhocbatches or
modules...
http://blogs.msdn.com/sqltips/archive/2005/10/05/To

• Troubleshooting Performance Problems in SQL

Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/20

• Processing XML Showplans Using SQLCLR in SQL

Server 2005
http://msdn.microsoft.com/library/default.asp?url=/li
SEAS09
Q&A
64
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The
information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

SEAS2009 Query Optimization Final

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SEAS2009 Query Optimization Final

Uploaded by

Copyright:

Available Formats

SEAS09

 international and technology SQL

– ISV team SQL

– Best practice team

SQL Server Design-win

SQL Server Relational Server

Language Processing (Parse/Bind/View Expansion)

Backup / Restore, BCP, …)

Selection, Join Ordering,

SQL Relat ional Server

SQL Server Relational Server

Language Processing (Parse/Bind/View Expansion)

Backup / Restore, BCP, …)

Selection, Join Ordering,

Statistics, Costing) (Query Operators,

SQL Relat ional Server

SQL Server Relational Server

Language Processing (Parse/Bind/View Expansion)

Backup / Restore, BCP, …)

Selection, Join Ordering,

Ind e x Se le ct ion, Join (Query Operators,

SQL Relat ional Server

| SQL Server Customer Advisory Team

| SQL Server Customer Advisory Team

Join Join Join

Join Join Hash-Join

Filter (A.x = 5) B GroupBy A.x, sum(A.y) B A B

Simplification Exploration Implementation

| SQL Server Customer Advisory Team

• Join reordering • Star and Snowflake

| SQL Server Customer Advisory Team

| SQL Server Customer Advisory Team

SQL Server Cost-based Query

search(0) search(1) search(2)

use explorat ion and

| SQL Server Customer Advisory Team

IBM DB2 On NT And UNIX

lNon-uniform query represent at ion

| SQL Server Customer Advisory Team

SQL Server - Optimizer

Tools to monitor optimization

What affects optimizer

Query Plan aka Showplan

• Run time info SET STATISTICS SET STATISTICS Include Actual

Demo – Showplan in SSMS

Actual Query Plan

Demo – Trivial Plan in SSMS

Demo - Optimizer Warnings

Demo – Database Tuning

Query Plan Debugging – best

Optimizer Hint Classification

dbo.Products JOIN HINT

ON [Order Details].ProductID = Products.ProductID

OPTION (RECOMPILE, LOOP JOIN)

Optimizer Hint Examples

Hints - New in 2005 and 2008

Optimize For Hint

• Values are used only for the

Use Plan Hint

What’s Forced by Plan Hint

Plan Hint Limitations

Plan Guides - Idea

modified directly in the source code yet