No, when a plan is flushed from cache, it's gone forever. The only thing you can do is try to capture the plans regularly (based on how often they flush...

It adds overhead, but it's pretty trivial. The accumulative effects aren't good, but you're unlikely to see any given query perform badly because of this.

Please, edit the post, remove the XML. Then go back and save your execution plan as a .SQLPLAN file. You can then post the file as an attachment. From there...

From the Books Online:

The missing indexes feature is on by default. No controls are provided to turn the feature on or off, or to reset any of the tables returned...

Dynamic methods are frequently problematic, but to get the data you're looking for, check out the system views available under the schema called INFORMATION_SCHEMA. They should supply you with everything...

To be able to use all the methods and abilities of 2008, you will need to set the compatibility mode to 2008, not 2000. Performance may or may not...

Paul White NZ (5/19/2010)

---

That sort on SchID is an optimisation for sequential I/O.

Look at the loop join after the sort operator...

If you right click on the plan and "Save As" a .sqplan file, you can post this online so that we can see more information. But, you do have an...

I freely admit I'm not smart enough to always figure out or understand why the optimizer did something. All I can say is what I see. The place where the...

J-F Bergeron (5/18/2010)

---

Are those queries on the same server? If no, then I'm guessing 1 of the server needs to have its statistics updated. You can see 1 of the...

The difference I'm seeing is in where the DISTINCT operation is applied. Of those two plans, the faster plan has a HASH aggregate while the other does a completely useless...

I wouldn't be surprised if you see an operator in the execution plan called Key Lookup. If it's there, you're looking at an instance of a covering index and a...

Pretty much. There may be another way around, but I don't know it.

Mike nailed it pretty well. I can't add much.

But I'll say this. Imagine a piece of TSQL code that, let's say, inserts data into three tables. You can put a...

That's a huge topic. I have a chapter in a book I'm writing for Red Gate waiting for tech edits on this exact topic right now.

There are any number...