Disabling Shared Memory - SQL Native Client Configuration
Posted on 2009-04-14
We have 5 front end Windows Server 2003 servers connecting to a Dell R900 server with 24 cores. All machines are 64 bit operating systems. We have started seeing this error:
---> System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
I have read many articles saying that we should disable Shared Memory in the SQL Native Client Configuration, and set the order of the TCP/IP client protocol to 1.
By disabling Shared Memory - what effect will this setting have on our current web applications? If we are connecting to SQL Server using the SQL machine name, will we be affected? I want to make sure our applications do not break.
Isn't Shared Memory only used if a connection to SQL is made locally?