J
JohnE
Hello. This is about a SQL Server 2005 back end and Access 2007 front end.
There is a front end on each user's machine. This has to do with the locking
(or blocking as some call it) issue. Connections from the front end remain
open once the user opens the front end until the front end closes, if the
user closes the front end at all and not everyone closes the front end when
done. There can be approximately 100 (+/-) people using the front end during
the day. Some may actually be transmitting data (transactions) and some may
not. But my thought is if the connection is always open, whether a user is
actually working on the front end or not, it is still transmitting
information if nothing more than updating all the open front ends. The more
staff that use their front end, the more connections and data flow.
How is this affecting the server performance? Does connection pooling come
into play? How do other organizations manage the connections as well as
locks or blocks?
Thanks.
John
There is a front end on each user's machine. This has to do with the locking
(or blocking as some call it) issue. Connections from the front end remain
open once the user opens the front end until the front end closes, if the
user closes the front end at all and not everyone closes the front end when
done. There can be approximately 100 (+/-) people using the front end during
the day. Some may actually be transmitting data (transactions) and some may
not. But my thought is if the connection is always open, whether a user is
actually working on the front end or not, it is still transmitting
information if nothing more than updating all the open front ends. The more
staff that use their front end, the more connections and data flow.
How is this affecting the server performance? Does connection pooling come
into play? How do other organizations manage the connections as well as
locks or blocks?
Thanks.
John