CFQUERYPARAM does increase the amount of processing that is required to run a query on the first execution, but subsequent executions should be faster (assuming your database can leverage prepared statements). I have seen CFQUERYPARAM creating a dramatic increase (as you see) in query execution times once or twice. I can't recall exactly the scenario, however.
As long as you do proper data validation and cleanup, it's safe to leave the CFQUERYPARAMs out to save that 10 seconds, but make sure your validation is *tight*. cheers, barneyb On 12/28/06, Greg Luce <[EMAIL PROTECTED]> wrote: > OK, I must have something wrong here. I've only heard good things about > cfqueryparam on this list for both security and performance. A client sent > me an ugly report that times out for them. I spent an hour going through it > and applying cfqueryparams to each variable in the many queries with > appropriate datatypes. I threw a cfsetting tag in to increase the request > timeout and the report runs in roughly about 512687 ms, restarted MSSQL > server and CFMX7, then with the cfqueryparams the same query that was > running in 5282ms in the old code, now takes 15094ms. > > Any ideas? > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265229 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
