TCP is the key as this is the protocol used to communicate from Service Desk DB agent to MS SQL Server when MS SQL Server resides on a separate machine. Moreover, you can implement these Microsoft Operating System configuration changes to further provide stability. Running a stream that exports many records into a SQL server database will cause the following error: 4 MicrosoftODBC SQL Server DriverDBNETLIBConnectionWrite (send).
I have a 3rd party application that is reading tables from SQL Server 2005 Express. Last night I set the program running on a continuous loop that reads values from a few tables, and updates a 'heartbeat' record every few seconds - nothing else.
This morning I found that after running for about 4 and a half hours it crashed with the following message:Number = 0x80004004Source = Microsoft OLE DB Provider for SQL ServerDescription =DBNETLIBConnectionRead (recv).General network error. Check your network documentation.SQL State = 08S01NativeError = 11I am running it on a machine operating on Windows XP Professional SP2 and the version of SQL Server 2005 I am running is 2005.090.1399.00. The 3rd party application is running on the same machine as SQL Server. The only systems that interrogate the table are:1. The main program thread of the 3rd party application that does the work mentioned above.2. A MS Access front end that interrogates some of the tables (linked) once every 5 seconds using an On Timer Event3 There are 8 other threads running that are linked to the database on the 3rd party application but, when the application is idling as it was overnight, they do not interact with SQL tables at all.There are a total of 7 tables, the largest having 99 records.I have no idea what this message means or what to do to prevent it from happening.
I chose SQL Server because I thought it was going to be robust but this is not inspiring confidence. Can anyone help me understand this message please?.