Connection Breaks on StProc text UPDATE

Hi,
We have a simple stored procedure that has a text parameter, among others.
Inside the procedure the text parameter is assigned to a text column in a
simple SET clause of a simple UPDATE statement. We pass a 15 character
string as an argument for the parameter, and even though the string is
stored to the table, we get this error message (running in Query
Analyzer)...
*-*-*-*
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
*-*-*-*
Any of the following make the error message go away...
1) Pass NULL as the argument
2) Comment out the assignment in the SET clause
3) Change the parameter to varchar(8000)
Anyone have any ideas?
--
Thank you,
Daniel Jameson
Children's Oncology Group
http://www.childrensoncologygroup.orgCan you show the CREATE TABLE statement and the CREATE PROCEDURE code?
Also, tell us the result of SELECT @.@.VERSION
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"danjam" <djameson@.childrensoncologygroup.org> wrote in message
news:e6y2#eMxDHA.3416@.tk2msftngp13.phx.gbl...
> Hi,
> We have a simple stored procedure that has a text parameter, among others.
> Inside the procedure the text parameter is assigned to a text column in a
> simple SET clause of a simple UPDATE statement. We pass a 15 character
> string as an argument for the parameter, and even though the string is
> stored to the table, we get this error message (running in Query
> Analyzer)...
> *-*-*-*
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> *-*-*-*
> Any of the following make the error message go away...
> 1) Pass NULL as the argument
> 2) Comment out the assignment in the SET clause
> 3) Change the parameter to varchar(8000)
> Anyone have any ideas?
> --
> Thank you,
> Daniel Jameson
> Children's Oncology Group
> http://www.childrensoncologygroup.org
>|||There are some known bugs that cause this or similar errors - it would
help to see your stored procedure. It could be an issue with UNION,
with an INSTEAD OF trigger, certain query structures, or an unknown
bug... It does sound like a bug, though.
SK
danjam wrote:
>Hi,
>We have a simple stored procedure that has a text parameter, among others.
>Inside the procedure the text parameter is assigned to a text column in a
>simple SET clause of a simple UPDATE statement. We pass a 15 character
>string as an argument for the parameter, and even though the string is
>stored to the table, we get this error message (running in Query
>Analyzer)...
>*-*-*-*
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
>(CheckforData()).
>Server: Msg 11, Level 16, State 1, Line 0
>General network error. Check your network documentation.
>Connection Broken
>*-*-*-*
>Any of the following make the error message go away...
> 1) Pass NULL as the argument
> 2) Comment out the assignment in the SET clause
> 3) Change the parameter to varchar(8000)
>Anyone have any ideas?
>
>|||Steve,
Thank you for responding. I have posted additional info under Aaron's post.
I do have an INSTEAD of trigger, but there are no UNION's involved.
--
Thank you,
Daniel Jameson
Children's Oncology Group
http://www.childrensoncologygroup.org
"Steve Kass" <skass@.drew.edu> wrote in message
news:uIFJ5pMxDHA.2556@.TK2MSFTNGP10.phx.gbl...
> There are some known bugs that cause this or similar errors - it would
> help to see your stored procedure. It could be an issue with UNION,
> with an INSTEAD OF trigger, certain query structures, or an unknown
> bug... It does sound like a bug, though.
> SK
> danjam wrote:
> >Hi,
> >
> >We have a simple stored procedure that has a text parameter, among
others.
> >Inside the procedure the text parameter is assigned to a text column in a
> >simple SET clause of a simple UPDATE statement. We pass a 15 character
> >string as an argument for the parameter, and even though the string is
> >stored to the table, we get this error message (running in Query
> >Analyzer)...
> >
> >*-*-*-*
> >[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> >(CheckforData()).
> >Server: Msg 11, Level 16, State 1, Line 0
> >General network error. Check your network documentation.
> >
> >Connection Broken
> >*-*-*-*
> >
> >Any of the following make the error message go away...
> > 1) Pass NULL as the argument
> > 2) Comment out the assignment in the SET clause
> > 3) Change the parameter to varchar(8000)
> >
> >Anyone have any ideas?
> >
> >
> >
>