TCP/IP Connections & ODBC Errors
Posted on 2013-06-26
I am using Win7 Pro PC as a SQL server with SQL 2008 Express R2. This serves a local database application to about 6-7 workstations.
Time to time, I get random ODBC errors, which I believe gets worst at busy times, sometime restarting the application helps temporarily, but a bigger relief is when I shutdown everything, restart the server, then start everything up again.
I have read that Win 7 is limited to 20 concurent TCP/IP connections and i am thinking that ODBC is related to this because when I open a particulat form in my application, I have my main recordset, but I also have around 5 or 6 dropdowns, which are populated with their own recordsource. So, one record equals to about 7 connections.
i am not a great network p[erson, I am programmer and I do close my recordset as soon as I can, but there are still live concurent connections sometimes.
As a not network person, could you guys confirm my theory above because I also read that Win Server OSs (2003, 2008, 2012?) have unlimited TCP/IP concurrent connections, and I wanted to get some thoughts on this before I venture off into getting a new server.
As well, going back to the 20 concurrent TCP/IP connections, if there any way I can check the number of live TCP/IP connections on the spot?