March 25, 2005 at 9:14 pm
Hi All,
I have stored proc that processes about 60,000 rows using a cursor. When I call the SP from Query Analyzer, I get the following error message after processing about 12,000 records :
Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
12614 records
What can i do to make this SP run sucessfully ? I even tried using a table variable instead of a cursor, but got the same result.
THE output from SP_CONFIG is
Option config_value
----------------------------------------------------------------------------------------------------------------------------------
| affinity mask | 0 |
| allow updates | 0 |
| awe enabled | 0 |
| c2 audit mode | 0 |
| cost threshold for parallelism | 5 |
| Cross DB Ownership Chaining | 0 |
| cursor threshold | -1 |
| default full-text language | 1033 |
| default language | 0 |
| fill factor (%) | 0 |
| index create memory (KB) | 0 |
| lightweight pooling | 0 |
| locks | 0 |
| max degree of parallelism | 0 |
| max server memory (MB) | 2147483647 |
| max text repl size (B) | 65536 |
| max worker threads | 255 |
| media retention | 0 |
| min memory per query (KB) | 1024 |
| min server memory (MB) | 0 |
| nested triggers | 1 |
| network packet size (B) | 4096 |
| open objects | 0 |
| priority boost | 0 |
| query governor cost limit | 0 |
| query wait (s) | -1 |
| recovery interval (min) | 0 |
| remote access | 1 |
| remote login timeout (s) | 20 |
| remote proc trans | 0 |
| remote query timeout (s) | 0 |
| scan for startup procs | 0 |
| set working set size | 0 |
| show advanced options | 1 |
| two digit year cutoff | 2049 |
| user connections | 0 |
| user options | 0 |
March 27, 2005 at 4:24 pm
It's difficult to diagnose this message without more information.
Could you post the SP code and any relevant table schemas.
Also, check the SQL Error Log and machine event logs for any network related problems.
Scott Thornburg
March 28, 2005 at 8:18 am
Try increasing your network package size under the Connections Tab of Query Analyzer's Options
Gary L. Fry
Senior Database Administrator III
MCTS, MCITP SQL Server 2008 Database Administration
Colonial Life/UNUM
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply