Hi All,
I have a large number (65+) of VB clients that need to access an ODBC-Compliant DB, possibly simultaneously. My current solution has each client opening a connection directly to the database with VB ADO calls, however, I am fairly sure that this is not the best implementation in terms of perfomance as it has no centralised pooling of connections to the database.
In my mind, I am thinking that the most efficient way of accessing the database would be through a "pooler" of some sort that will hold/queue all requests to the database and return the results to the client machine. I am thinking this would require designing an adapter that will reside on a separate (query) server and that will accept requests from the client machines, subsequently passing the SQL query on to the database? (This seems a bit complex as it would require the design of a queuing mechanism as well as a registration mechanism for each client to register with the query server.)
Does anyone know of a simpler method of achieving this? It is entirely possible that I am making this issue more complex than it really is, however, I am not sure if there is an easier way! Would 65 simultaneous client connections to an ODBC database actually cause noticable performance issues??
Thanks very much in advance!
