Multi Statement Query Plans

This video explains what to expect in your execution plan when running multiple statements in sql management studio.

I'm currently working for FM Global, an industry leading engineering & insurance company, as a DBA. I've done development of large scale applications in languages such as VB, C# and Java. I've worked in SQL Server from the hoary days of 6.0. My nickname at work is the "The Scary DBA." I even have an official name plate with it. I wear it proudly. I was awarded a Microsoft MVP in April of '09.

AQ on 8/4/2009

Very Informative Thanx

Martin Poirier on 8/4/2009

Good presentation of the execution plan, knowing that you have issues with a particular scan or filter can be useful. I would like to have a future presentation that gives hints on how to resolve the time consuming parts of a query base on the report of the execution plan.

Robert Neal on 8/4/2009

video explained something that is very obvious to anyone.

Ray on 8/4/2009

Could use more detail on the meaning behind the cost. Why a number like 0.3475678? How is it dervied?

Grant Fritchey on 8/5/2009

I'm glad a few people found it useful. The numbers are derived from the cost estimates used by the optimizer based on statistics. These are a general estimate, measured in terms of seconds, based on an old machine that was on someone's desk at Microsoft back in the '90's (or so the story goes). They're not accurate measurements of reality, but they do show how the optimizer arrived at its decisions.

Girish kalwadia on 8/5/2009

good one

Sneha on 8/12/2009

I would like a presentation on how to interpret the query plan shown and then optimize the query based on that

Team FAB on 8/12/2009

I've already seen this one. Do you send out repeats in the daily email?

Julie Breutzmann on 8/12/2009

Thanks, Grant. Your short videos are very helpful for someone like me who is just starting to learn how to use and interpret execution plans.

Keith on 8/13/2009

While I appreciate execution time analysis, I think it would be more useful to compare two queries having different estimated times yet which return the same data.

Grant Fritchey on 8/14/2009

But the same query can have different estimates as the underlying statistics change. That's why relying on estimated values is quite frankly dangerous.

F6F46BB996 on 10/15/2009

Thank you.

sunil on 10/22/2009

good one

J Delilah Webb on 4/6/2010

Not being aware of this functionality, I have been doing comparisons the hard way. This will save a lot of time. Thanks!

digish on 12/30/2011

Could have loved to listen query optimization

KSRINI on 12/30/2011

can be more elaborate with some more examples

Steven Robinson on 12/30/2011

Ok Video

Saikumar on 12/30/2011

Good video with clear voice

shankar on 1/1/2012

thanks

Nimesh Parikh on 1/3/2012

Very Basic, was expecting much more

Sean on 1/3/2012

:)

David Adams on 1/13/2012

more of the optimizer would be great