• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "PM for SQL Server 2008"

Collapse

  • suityou01
    replied
    Originally posted by d000hg View Post
    Pot, kettle...
    Reeeeeeaaaaaaalllly?

    Leave a comment:


  • d000hg
    replied
    Originally posted by suityou01 View Post
    Excellent first step. Now, as a mere suggestion, try reading it.

    Pot, kettle...

    Leave a comment:


  • suityou01
    replied
    Originally posted by mudskipper View Post
    Yep - I've got it bookmarked.
    Excellent first step. Now, as a mere suggestion, try reading it.

    Leave a comment:


  • mudskipper
    replied
    Originally posted by suityou01 View Post
    Yep - I've got it bookmarked.

    Leave a comment:


  • suityou01
    replied
    Execution plan basics

    HTH

    Leave a comment:


  • DimPrawn
    replied
    Originally posted by mudskipper View Post
    Yep, if you've got the original plan...

    Leave a comment:


  • suityou01
    replied
    Originally posted by mudskipper View Post
    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
    Get Bob to fix it.

    Leave a comment:


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

    Leave a comment:


  • mudskipper
    replied
    Originally posted by DimPrawn View Post
    USE PLAN query hint.

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

    Leave a comment:


  • DimPrawn
    replied
    USE PLAN query hint.

    Sorted.

    Leave a comment:


  • mudskipper
    replied
    Originally posted by KentPhilip View Post
    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.

    Leave a comment:


  • doodab
    replied
    Originally posted by KentPhilip View Post
    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...

    Leave a comment:


  • eek
    replied
    Originally posted by KentPhilip View Post
    When did you last update the statistics on the database(s)?
    My guess is over a year ago.

    Leave a comment:


  • KentPhilip
    replied
    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.

    Leave a comment:


  • mudskipper
    replied
    Originally posted by MarillionFan View Post
    A poor work(wo)man always blames ClientCo's tools.
    FTFY

    Leave a comment:

Working...
X