Ben Mueller wrote: > We hit a problem with morning relating to cfqueryparam. A query using > cfqueryparam referenced a table whose structure had been changed (we added a > column). It appears the execution plan had been cached, and either CF7 or > SQL Server 2000 wasn't smart enough to figure out that the table had changed, > and so the query bombed.
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. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:296666 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
