|
Comments
|
|
How is saving the execution plan in XML any better than saving the plan as a sqlplan originally? You said it has a 'rich' amount of information. What do you get in XML that you wouldn't otherwise get?
|
|
|
good
|
|
|
Good stuff!
|
|
|
To C G:
What you get is XML. That means it can be queried. Remember, in 2005 and above, the execution plans are XML, just that in 2005 some of the data is hidden (missing indexes for example), but in 2008 all of the xml data is visible in the graphical plan either right on the plan, through a tooltip or through the properties. But you still can't query against it or browse through it quickly. The information in the XML is rich, but it's not necessarily different (except in 2005).
|
|
|
Very Interesting, It may be necessary in future.
|
|
|
Very Interesting, It may be necessary in future.
|
|
|
cool. Very handy tip
|
|
|
very compactly explained.
|
|
|
Excellent! Thank you for sharing this information. I had no idea this could be done until now. Thanks again!
|
|
|
needs an update for SQL 2008
|
|
|
Superb!!!!!
|
|
|
very cool, i had no idea you could do this.
|
|
|
I don't have much experience working with XML, so info like this is very helpful. Thank you for creating it. I would be interested in seeing a follow-up video on how to XQUERY the XML plan file.
|
|
|
would be good to know how to automate collection, and examination of the xml plan - since it can be queried, but the vid does not show how to carry it to the next level which would be more useful for practitioners.
|
|
|
This video covered what they were, but not so sure about "why they are useful" ... maybe that you can save them? But I always enjoy the teaser.
|
|
|
Small plus rich in info video. Just to-the-point. Thanks.
|
|
|
Nice - ability to convert the XML plan to visual SQL data plan
|
|
|
Excellent Video, Author had a good grasp of the subject
|