Hello, I'm about to engage in discussions regarding the various possible ways to redesign my company's application tier. Some approaches grab quite a few database connections and hold onto them for some time before reaping them back, and I'm concerned about the possible cost. I am hoping to get a feel for the amount of CPU work required for DB2 V7.2 Solaris to manage a large pool of mostly idle connections. I'm also interested in knowing if it is less expensive for the server to manage an overly large pool of idle connections than it is to authenticate a steady stream of connection requests, which would keep the overall number of concurrent connections much lower. If anyone on this list has some good pointers in this area, I'd be glad to hear them. Thanks, Fred Sobotka Database Administrator IBM Certified Solutions Expert - DB2 UDB V7.1 Administration for Unix, Windows, and OS/2 CollegeNET, Inc. - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
