From: Walden H. Leverich
In my case I don't draw the line, each request is a "new"
connection [from the pool]...
I appreciate the response. And it sounds like a textbook answer. Do you see any dilemma occurring as the number of applications increases, and consequently the number of tables opened in the database server jobs increases? A financial system may not use the same tables as a human resource system, but if all applications get connections from the same pool, it seems to me that the server jobs will end up maintaining open data paths to all the files in both systems. A user may have opened a table under one connection, but if that connection is not available for a subsequent request, then the table is reopened in another connection.
Nathan.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.