We are trying to track down a performance issue.
One theory we have is that we are running out of connections in the connection pool.
Is there a way to monitor the size of a connection pool?
Sql-server – monitoring the size of an SQL Server connection pool
connection-poolconnectionssql serversql-server-2005
Related Solutions
The default size of connection pools is 100. You can change that size in in the connectionstring itself, using the parameter:
Max Pool Size
See here for a complete list of connectionstring parameters.
You should have a good reason to do that. In most cases where you run out of connections, they are leaking (=not properly closed) in the application. If you have access to the source code I would consider closing the connections as soon as the query was executed.
What needs to happen is that the MTU setting on the ethernet network needs to be increased from 1500 to something north of 4096. These settings are typically set on the Driver settings page. For good networking you really want all devices (including all ethernet switches) on the same ethernet to have the same MTU setting.
(source: sysadmin1138.net)
That's where you'd change it on one of my servers.
Can it help? It certainly can. Less packet fragmentation means less work on the TCP stack to reassemble the traffic stream. It may not be orders of magnitude, but it could help.
Connections local to the server use, I believe, pipes rather than TCP connections and are probably unaffected by this change.
Best Answer
Have a look at these performance counters:
http://msdn.microsoft.com/en-us/library/ms254503.aspx
Some of these counters require a change to the app.config file