Chris Hughes
ProgressTalk.com Sponsor
Hi
I'm hoping that somebody can explain to me why the OpenEdge implementation of the SQL dataserver requires so many connections for each physical user to a SQL database?
It is likely I'm going to start trialing different pf file parameters but just want to understand the underlying technology and the way it works first.
So we have a parameter to control the cache connections from the Dataserver, but then also the ODBC SQL Native client has its own multiple connections capability as well....
Our software can easily go 20 connections or more in a session for one user.
So how does this work, can one connection only handle one open cursor ie 3 connections requred for....
for each customer (1 connection)
Any help very much appreciated.
Thanks
Chris.
I'm hoping that somebody can explain to me why the OpenEdge implementation of the SQL dataserver requires so many connections for each physical user to a SQL database?
It is likely I'm going to start trialing different pf file parameters but just want to understand the underlying technology and the way it works first.
So we have a parameter to control the cache connections from the Dataserver, but then also the ODBC SQL Native client has its own multiple connections capability as well....
Our software can easily go 20 connections or more in a session for one user.
So how does this work, can one connection only handle one open cursor ie 3 connections requred for....
for each customer (1 connection)
for each invoice (1 connection)
for each invoiceline (1 connection)
Any help very much appreciated.
Thanks
Chris.