July 1, 2011 at 4:24 am
Please find atttached two execution plans:
In SPROC_GETEVENTFORCASEEX3, Clustered Index seek is taking 38% - tblSessionVars
In SPROC_UPDATEPROPERTYDATA5, table delete is taking 36% - tblRuleStack and tblRuleStackEx
Please suggest how this can be optimized.
Many thanks,
Vijay
July 5, 2011 at 2:33 pm
you can create a non clustered index to replace the IX_SessionVars. At this point is doing what its suppose to which is 24 seeks, against the table. you can make it a little faster by doing 24 seeks against a non-clustered. my guess it will help a little but not much. it already doing a nested loop, as should be with 24 rows.Now this all holds true IF and only IF the actual and Ests are close.. you have the est qry plan. it Statistics are off then that changes everything.
you should capture and actual so we have est vs actual. this will give us a better idea
as far as the deletes go not much in the way you can tune that....remember every time you do a delete it has to do read first
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply