That last post makes me think of indexes. Since you changed the code to make things simpler and the database isn't maintained, check to see if the procedure is using any of your indexes. If, say, a change resulted in a full table scan, that would explain the performance degradation. It could be that a single covering index isn't being used any more. If it is using the indexes properly, then definitely go with updating the statistics. Just food for thought.