Please give your suggestions to resolve this problem.
Index Seek on Non Clustered Index cost is very high (92%) how to reduce this ?
I've run into this in the past. Like Gail says, not enough information to call out a fix but, if it were me, I'd check the properties of the Index Seek in the execution plan and see how many times it's executing. If it's doing 1 seek per row instead of a single seek and a range scan, that could be one of the problems.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs