as long as you are using a db that supports multiple sql statements per cfquery tag, you really aren't killing your db that bad.  move it to a stored proc and you are really g2g.

I had an app using a self-referncing table that had to do ton of recursive loops with recordsets looping and doing a couple-3 queries for each record in the initial record set.  MS access was taking 4000+ ms for page render; ms sql with a single cfquery and a ton of sql statements and cursors and the like in a single cfquery tag was sub-100ms.

I think the biggest hit is cf making the odbc connection, especially if you have good indexes and a cached query plan(stored proc or cfqueryparam).  Can another cf guru on the list verify?

-----Original Message-----
From: [EMAIL PROTECTED]
To: CF-Talk
Sent: 2/13/04 9:19 AM
Subject: Re: Update query record count?

I had in working in a 2 part w/ select, but was hoping to cut down to 1
query
since it's being hit on every page to lower the DB load if possible.
  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to