Thanks, Jochem, for the reply. I glanced at that call just briefly; does it clear *all* stored execution plans, or just a specified one? It seems like the only way it would be useful in this context is if it cleared them all, since we have no way of knowing which plans are cached.
A larger question is this: isn't this a huge headache for everybody? We update our site a lot--sometimes several times a day--and if having <cfqp> around means we need to add an extra step to our process of getting stuff out to our production servers, that just seems like a big pain. Maybe I'm asking for too much here, but I suppose I would expect that if a cached execution plan bombed in SQL Server, it would automatically attempt to re-compile, under the assumption that the cached plan is out of date. Thanks again, Ben > The execution plan is cached in the database so there is no way CF > could > possible know it is cached, let alone the cache needs to be flushed. > > > > ....and it seems the only solutions are to cycle the CF service or > change any query (in some minor way) to force CF to create a new > execution plan. > > What you need is to flush the cache in the database server. Look into > > DBCC FREEPROCCACHE and its cousins. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:296672 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
