My gut feeling is that you should not enable this feature unless you know specifically why you want to use it.
Have had trouble in the past with the DBMS running out of connections on busy servers with this setting enabled, as every client has a connection whether they are using it or not (eg. you will collect idle connections). The overhead in creating a connection per request is most likely low, especially when connecting locally or even over a LAN. May be interesting to gauge whether you are getting any performance benefits with this setting enabled / disabled just by setting some timers and running a few queries. On Sun, 2008-04-27 at 18:19 -0700, Nathan Drury wrote: > Hi > > We have a CF app which can be using multiple DBs at any given time > (e.g. user1 logs into DB1, user2 logs into DB2, etc). At any given > time the application can be accessing up to 20 different DBs. I've > been trying to determine whether we should be maintaining connections > to these DBs or not. I've found very little information out there > about it except that as a general rule you should maintain connections > and that you should limit connections to be the number of maximum > simultaneous requests (per CF8WACK2). > > However, a colleague claims to have had issues in the past with the > app when maintain connections is turned on (but this may have been due > to a known issue with CF6.1 - > http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_18980&sliceId=1). > > Can anyone shed some light on when NOT to maintain connections? > > Thanks > > Nathan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
