Connection Pool Implementation Strategy
===

I am working on a Application in which there are 200 different client. Each client has there own database (all Tables and setup are same). Each client data has to be separate and privacy of data is really important and hence cannot have single central database.

hence currently there are 200 Data Source on WebSphere Application server. currently the min count was set to 0 and max was set to 30 for connection pool.

now there are 2 problems :

1. To find the default active connection that can be possible and its footprint. (got to know that each connect require around 2 to 4 MB of space).

2. When a new connection is created, all queries that run on this connection is slow since the access plan and ODP are not created. how can this be overcome? we call this issue hydration issue since after the first run of any query subsequent run faster.

any ideas , feedback or suggestion is welcome.