The problem is that on some of our larger customers, they may have 50 or
more people each running an average of 10 or so programs at a time from the
menu.
Each program has a database connection, and up to 30 query components.
Since this creates a seperate database connection for each program, some of
our clients are starting to experience some serious performance issues on
the database because of all the open Oracle connections.
Is there any way the main application can open a single connection to the
database, and the spawned programs share that database connection component?
Datasnap kind-of allows us to do this with datasets, but it requires all of
the datasets to reside on the application server. In our case each program
does something entirely different with the data, so putting all the datasets
in an application server really won't work well for us. Also, our product
consists of literally hundreds of executable programs executing thousands of
different queries on around 100 tables, it would be a nightmare to try to
put all the necessary datasets in a single application server.
We really need to share the database connection, but have the datasets
themselves in the individual executable programs.
Thanks for any ideas here.
Lance Robaldo
La...@Robaldo.com
you could have 3 application servers,each managing one separate service.
each server
could maintain one database connection (3 total connections).users would
connect to diffrent servers
to perform their transactions. imagine for example one client program having
2 socketconnection components
to connect to the 2 services.
you could even divide the database itself in diffrent parts (something like
a distributed database) in order to
increase the performance.
this way you would have much less database connections, you could increase
the performance by isolating
the services in diffrent servers.the system could be managed and updated
easier. the most serious issue i think
is that you use (if i uderstood correctly from "access an Oracle database")
only one database
for all tables.try distributing the database and balance the workload in
diffrent servers.
as i said im just a student so i dont think that my proposed solution is
very professional or valid since
i dont have must "real life" experience in these situations.sorry if the
above was st...:):):):)
thanks
"Lance Robaldo" <RRob...@wltsoftware.com> wrote in message
news:46a0c33c$1...@newsgroups.borland.com...