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!
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.
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.
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.
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: