Eric: there's a couple of articles on allaire.com. Just search for 'query caching'. Basically, query caching is a Good Thing, as long as you use it sensibly and handle it correctly. A few points to consider: Query caching only applies to queries of the same name and with the same (exact same) SQL. Within the timeframe of the cache, any changes that are made to the data within the result set will not be returned; if you want changes to be available immediately, you need to refresh the cache. You need to consider how long you will accept data to be out of date for. If you have a heavy load site, caching a query for 3-4 seconds will improve performance without your data being out of date: Person A requests the query, it is cached. People B,C,D,E,F,G,H all request the same query within the next 3-4 seconds and reeive the cached version. Person A refreshes their screen immediately and, since the timeout will have passed, will receive a refreshed data set.
-----Original Message----- From: Carlisle, Eric [mailto:[EMAIL PROTECTED]] Sent: 01 November 2001 20:03 To: CF-Talk Subject: Caching Queries An application I am working with is really bogging down a database server. Can anybody point out an online resource to the pros/cons of caching queries? Maybe I'm making this more than it is and it's not that complicated. I'm just wondering if caching queries is an eventuality for web applications that get a lot of traffic. Thanks, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
