Okay, on option 3, with multiple DB drivers, what if you loaded up multiple
instances of the same driver? I dunno how this could be accomplished, but I
think its worth a look at.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: John Foulds [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, September 01, 2000 9:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Theory: Multiple ODBC conns?
>
> (1) More DSN's means more connections through the driver to the DB which
> means additional load on the driver, which probably works against any
> gains.
>
> (2) More DSN's means you can't connection pool as well, since the pool is
> assigned per DSN and not globally (ie. more inefficient connections as
> there
> is a greater possibility of idle connections).
>
> (3) Interestingly enough, using multiple DB drivers instead of multiple
> DSN's could also give a performance boost. If your primary was overloaded
> and bottlenecking, using an additional type (vendor/access method) of
> driver
> could lessen the load without requiring more hardware.
>
> (4) SQL Server 2000 lets you go right to the DB with a SQL statement in
> the
> url without having to go through middleware. Which is scarry, but you can
> tone it down and allow: "URL access through server-side XML templates that
> are referenced from the URL. This provides direct access to SQL Server,
> but
> you're actually hiding the SQL Select statement, or query, inside an XML
> template. Therefore a lot of middle-tier code is unnecessary for
> interaction
> with the database."
>
> I wonder what performance difference there is in going through CF compared
> to passing through a server side XML template?
>
> John Foulds
> Ottawa, Canada
>
>
> ----- Original Message -----
> From: "McCollough, Alan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 01, 2000 8:01 PM
> Subject: RE: Theory: Multiple ODBC conns?
>
>
> > I actually thought about doing a round-robin DSN by saying
> > <cfset application.dsn_counter = 1>
> > <cfset this_dsn= application.dsn_counter mod 4>
> > <CFQUERY name="yeah right" datsource="#Evaluate("dsn#this_dsn#")#">
> > ...
> > <cfset application.dsn_counter = dsn_counter +1>
> >
> > After thinking about the round-robin DSNing, though, I thought it more
> > efficient to just declare a specific DSN for each major table in the
> app.
> > Either way could work, though.
> >
> > I was testing this multi-conn idea today with 2 connections, and it
> seemed
> > to work fine, however, I didn't have enough of a load to see a
> difference.
> >
> > 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.
------------------------------------------------------------------------------
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.
