This isn't purely a fusebox question, but I think y'all will appreciate
it...
I was thinkin' to myself (stop laffin'), on a high-traffic site, with a lot
of DB hits, could you speed the CF>SQL transaction process up by having
multiple ODBC connections?
Most of us (what an assumption!) set up an ODBC for a given app, and that's
it. We refer to it as "#application.dsn#" or some such variable.
But... What if we set up #application.dsn1#, #application.dsn2# and so on,
lets say 4 similar ODBC connections, which would of course, also be present
on the CFAS, all 4 pointing to the same datasource.
My theory is, if you know that your app has, say, 4 common SQL
queries/actions that aren't cacheable, you assign each SQL query its own
DSN, so it travels on a separate ODBC connection, even though its hitting
the same database
EXAMPLE
You have an app, and it calls upon a SQL db "Northwind", and this db has
four tables you are using, "Employees" ,"Customers", "Orders", "Products".
You create four ODBC DSN's at the CFAS:
Northwind_Employees
Northwind_Customers
Northwind_Orders
Northwind_Products
In your CF templates, whenever you do a CFQUERY that calls upon one of the
aforementioned tables, you use the associated DSN. If a query involves
multiple tables, you use the DSN of the table that bears the weight of the
processing burden (you can use Query Analyzer to find this out).
I haven't tested this out for speed or load-bearing ability, but I have set
up multiple DSN's to the same db. Has anybody experimented with this, or
debunked this idea? I'm curious and don't wanna re-invent the wheel if its a
flat.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
------------------------------------------------------------------------------
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.
