Hey - in regards to this topic I found an insiteful article in a Builder.com newsletter. Sometimes an SP doesn't give you the performance gains you think it could because of the query cache. I couldn't find a link to it on builder so I posted it on my blog.
http://blog.mxconsulting.com/ -Mk -----Original Message----- From: Joseph Flanigan [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 5:47 PM To: CF-Talk Subject: Re: Execute Query string w CFQUERYPARAM > Why it is better in your opinion to use stored procedures for insert/update/deletes? The quick answer is that stored procedures are pre-complied execution plans. To run in the database engine, every SQL statement is compiled into something the database people call execution plans. These plans are the code that change and read data. Whenever a query is run that changes the structure of tables, efficient query plans result in the best performance of the database. A rule I follow is that if any changes are made that result in any table index being changed then use stored procedures. Insert and deletes always change indexes, most of the time updates do too. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Protect your mail server with built in anti-virus protection. It's not only good for you, it's good for everybody. http://www.houseoffusion.com/banners/view.cfm?bannerid=39 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:181831 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54