Hello ,
You could also consider designing a buisiness logic component ,, this way
you could even cache frequently used data , using such an architecture
also called an (n) tier design or distributed application
will give you lots more benefits ( ability to cluster , reuse components etc
etc etc ) however this requires a complete redisign of your application .
Marina`s answer is a good one to try to see if it solves the problem , as
it normally is only a mather of adding a few lines of code to the program
to get this working
regards
Michel Posseth
"Marina" <so*****@nospam.com> wrote in message
news:ud*************@TK2MSFTNGP09.phx.gbl...
Opening a connection at startup, and then keeping it open the whole time,
does not scale well - as you have seen.
So, change your code to open/close connections when necessary to do work
on the database.
"Rui Dias" <rd***@rcsoft.pt> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi there!
I've got this situation:
One application server where the application is installed;
One DB Server where the VB.NET application opens two sqlconnections at
startup;
One intranet wich application users (about 100) use to connect via
remote desktop to the application;
Because each one one of them has his own session, if they all get
connected, I've got about 200 open connections to DB.
How can I avoid this situation? Is there a way share the 2 connections to
every users? Do I want this?
Any help, tutorials, links, etc would be appreciated to solve this
problem.
Thanks in advance,
Rui Dias