C
Curtis Justus
Hello,
We have a dotnet windows service that will be utilized by anywhere from
100 - 300 windows clients. They will be connecting using a singleton call.
What is the best practice for connecting from within the service to the
database? Should each call new up a new connection and then connect?
Should I maintain a single, static object that contains a SqlConnection
object that all calls within the service reference? I'm not familiar enough
with how ADO.NET would function under this scenario. It would seem if I had
only one connection, that there would be a lot of latency waiting for
readers to complete reads to the database.
Thanks in advance!
cj
We have a dotnet windows service that will be utilized by anywhere from
100 - 300 windows clients. They will be connecting using a singleton call.
What is the best practice for connecting from within the service to the
database? Should each call new up a new connection and then connect?
Should I maintain a single, static object that contains a SqlConnection
object that all calls within the service reference? I'm not familiar enough
with how ADO.NET would function under this scenario. It would seem if I had
only one connection, that there would be a lot of latency waiting for
readers to complete reads to the database.
Thanks in advance!
cj