Still, in that case, the DB will simply perform a recompile to find a more suitable execution plan-- a step which would have had been performed anyway had there not have been a cached plan. So the worst case scenario seems to be you would break even. Doesn't seem like you can go wrong with that.
~Brad -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 12:23 PM To: CF-Talk Subject: RE: Is cfqueryparam worth it? > In general, the more complex the query (multi table joins, > subqueries, that sort of thing), the more complex the > execution plan, and the greater performance benefit from > having that execution plan cached. On the other hand, the more complex the query, the more likely that an execution plan that's optimal for one set of values may not be optimal for another set! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:285987 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
