Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 460
  • Last Modified:

TCP/IP Connections & ODBC Errors

Hi Experts,

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?

Thank you
0
APD Toronto
Asked:
APD Toronto
  • 2
1 Solution
 
Rob StoneCommented:
You can check your current connections in Resource Monitor. Then click on the Network tab and drop down TCP/IP connections.

I think you are right on 20 concurrent connections, you can confirm here:
Go to Start > Run and type winver.
Click on Microsoft Software License Terms hyperlink and scroll down to Section 3 - Device Connections. This will tell you how many you can have connect.

You won't have an 'unlimited' amount of TCP/IP connections, but you'll have enough you won't need to worry about it.  I've read posts that 2003 people had 70,000 concurrent connections so your 20 won't worry it ;)
0
 
APD TorontoAuthor Commented:
Under winver I did confirm that it is 20.

Under the Resource monitor I found "TCP Connections" list, but how do I get exact number? In the same place, to the right, it sais "TCP Connections" 100, but it also changes to 500, but the limit is as we confirmed 20.

I was expecting to find a number between 0 and 20, but maximum 20.
0
 
Rob StoneCommented:
That will show all the TCP/IP connections to your client.

If you want to get more granular, you probably want to install Network Monitor 3.4 (free Microsoft download) and put a trace on. You can filter out by the conversation.

There are guides out on the web on how to use this, and YouTube vid's as well. Here is an example.
http://www.windowsecurity.com/articles-tutorials/misc_network_security/Network-Monitoring-Network-Monitor-34-Part1.html
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now