PM for SQL Server 2008

[mudskipper]

Dear SQL Server 2008

Please, please don't, without any warning or authorisation, ditch a query plan that has worked perfectly well and efficiently over a year and replace it with a plan that causes the query to run 120x slower.

Doing so is very annoying.

Many thanks
mudskipper

[MarillionFan]

Dear SQL Server 2008

Please, please don't, without any warning or authorisation, ditch a query plan that has worked perfectly well and efficiently over a year and replace it with a plan that causes the query to run 120x slower.

Doing so is very annoying.

Many thanks
mudskipper

A poor work(wo)man always blames their tools.

[mudskipper]

A poor work(wo)man always blames ClientCo's tools.

FTFY

[KentPhilip]

When did you last update the statistics on the database(s)?
I suggest you do that first, and see whether it starts to use the old (correct) query plan again.

[eek]

When did you last update the statistics on the database(s)?

My guess is over a year ago.

[doodab]

I suggest you do that first, and see whether it starts to use the old (correct) query plan again or breaks loads of others.

Well, it might...

[mudskipper]

When did you last update the statistics on the database(s)?
I suggest you do that first, and see whether it starts to use the old (correct) query plan again.

Did that. Didn't work. Users not happy, so had to resolve quickly. Adding ' OPTION (FORCE ORDER) ' seemed to do the trick, but guess this could happen to any query if the stats change.

[DimPrawn]

USE PLAN query hint.

Sorted.

[mudskipper]

USE PLAN query hint.

Sorted.

Yep, if you've got the original plan...

[GB9]

I suppose that with not having any SQL Server skills I shouldn't have changed it myself. But can you fix it?