>>I agree with Mike Cole.
>>
>>If you combine all the accumulated milliseconds that you will save for the entire life of the application running multiple instances of it you probably will not make up for the delay in deploying the application for wasting time in such a minute issue :)
>>
>>I think I have something in my signature that might apply here :)
>
>Essentially I re-designed the ExecuteSQLCommand procedure. We had 4 different versions of it for all the cases (Reader, returning formatted string, DataSet, Scalar Value and NonQuery).
>
>I now introduced enumeration for the type and put the logic into one procedure. I also introduced a few new classes that will remove the necessity of passing back and forth parameters by reference.
>
>But doing so I, of course, broke all the existing code we already have, so I'm up to serious changes. That would be an opportunity to re-visit code I've written and optimize while looking at it.

IMO that is generally not a good idea. It's more like an opportunity to break working code.