You typically won't see any cfqueryparam performance gains on low-usage queries and servers. In these cases, the reason for using them is typically security, standardization and best practices.
Under heavy loads, cfqueryparam (sql bind variables actually) can help your database cache queries, helping them not recompile each time. Performance like this is usually up there with stored procedures, as they pretty much boil down to the same things. Of course there are still those arguments about are ad-hoc sql statements faster than stored procs, etc. Basically, stored procedures are about equal to ad-hocs using bind vars. Plain-jane ad-hoc will reduce your performance and scalability under heavy loads. (but i'm not really an expert) -nathan strutz http://www.dopefly.com/ Michael T. Tangorre wrote: >>From: Michael Dinowitz [mailto:[EMAIL PROTECTED] >>Personally, I see no reason for a CFQUERYPARAM being used >>inside a CFC. It adds extra overhead and the protection that >>it provides should be provided instead by the CFARGUMENT tag. >>Does anyone see a reason for it in such a case? Data binding? > > > Interesting you bring this up. I have a small forums application where I was > not using queryparam to start (just to get going.. I always go back and add > them in). When I went back in and added the tag to all the query/procs I saw > no difference in terms of performance, what kind of numbers are you seeing > performance wise in terms of degradation? > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194819 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
