July 30, 2010 at 9:42 am
Short story...
We have a web application running on a database version that is BACKED UP AND RETORED version - EVERY NIGHT. (well, that is the decision of smart DBAs - who 'know' everything)
After the retore it seems 'update Statistics with FULLSCAN' is performed on the tables.
Some how, some simple USPs used by the application are timing out or taking very very long time to return simple result sets.
Marking for recompilation /recreating the problem fixes the issue temporarily.
My questions, is there any explanation as to what is causing the corruption of the execution plans?
Thanks,
ZE
August 2, 2010 at 4:12 am
I think Sql optimizer will create new exec plan acccording to the new statistics( after statistics update).
next Sp/function run would be smoother. am i right ?
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply