Stored procedures offer a resource independent solution to this problem. If
your using cf to cached data your causing performance issues on your
webserver, but with stored proc's you not. It doesn't store the data in ram
when you use stored procedures, just the execution plan. Which can
significantly improve query time execution. If you have the ram on your
webserver to support it, the best performance would be gained by using
stored proc's and then caching them as a session or application variable on
the webserver, hence you get the best of both worlds.
Rick
-----Original Message-----
From: paul smith [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 30, 2000 4:40 PM
To: Fusebox
Subject: RE: refreshing cached queries
Hmmmm... CF-cached query is in local RAM
DB-cached query is in RAM across the LAN.
You have any data that supports your belief?
best, paul
At 01:28 PM 10/30/00 -0800, you wrote:
>If your using a "real" database back end, you should really consider using
>stored procedures. That will prevent all the caching issues with
<cfquery>.
>Not only that but I fail to believe that the web server cahing a query will
>be as quick as a database backend's way of caching query's and thier
>executon plans.
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
