> LOL Dave, you crack me up. Hey, cut me some slack, I was eating pierogies.
> As far as your first question-- like Dave said, the only way NOT to use > a prepared statement is to drop the query param. Also, on this subject, > dropping the number of max pooled statements to 0 or unchecking maintain > connections in your data source settings will cause your prepared > statements to be unprepared after they are called so they are not reused > on subsequent calls. From my understanding, that doesn't necessarily > keep the SQL server from caching a reusable execution plan, it simply > means the statement must be re-prepared every time as opposed to the CF > server saying "hey DB, remember that one statement that I sent you > earlier that you told me to reference as prepared statement 37? I want > to call it again with these inputs". You can, however, use things like RECOMPILE hints to keep the prepared statement from being used with an existing execution plan: http://www.sqlmag.com/Article/ArticleID/94369/sql_server_94369.html Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more informati ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:324569 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
