Can anyone tell me if this behaviour of table is fine or do we need to sort out some issue.

Thanks Gail. Just for the information to all, I executed the sproc with "WITH RECOMPILE" option and thereafter it started working fine [back to normal time].

Ken, I've put this logic into a function along with some selective features so that indexes can be used and replaced this funciton frfom views used in stored procedures. All...

Sorry for this question. I have written the CTEs inside the function. Thanks ken, that was of great help.

Thanks Ken. Its really nice, however can we write a CTE inside a function ?

Sure, I'll check that way and let you know. Thanks Gail.

Thanks Steve, the document was wonderful.

Grant, Even i think its because of parameter snuffing. How can I get rid of it ?

Yes, we are migratng to new hardware.

Thanks Ashish.

Sorry Folks, After investigations we found it was because of rendering at frontend and not backend. Query is doing good.

Thanks Grant. What should be the generalized fillfactor for indexes on OLTP tables ?

I currently have one collation with case sensitive. Want to change it to case insensitive. We will use side by side migration.

Thanks Gail for all yur help. Your information links were great. I have brought down the effect of deadlock to big extent (with the help of your shared information), though...

Jeff, My scenario is simple. I have one stored procedure with lots of inserts and selects. There is just one update at the end of it updating say few thousand...

I've attached the execution lan for update statement.