Tuesday, March 20, 2012
[TCP/IP Sockets]ConnectionCheckForData (CheckforData())
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?
Hi Scott
Having DDL and sample data with the expected results from that data would be
nice. See http://www.aspfaq.com/etiquette.asp?id=5006
"Scott Sheen" wrote:
> MS SQL 2000.
> When I attempt a SELECT I get the following:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> The offending SELECT
> select a.account
> from table1 a
> where a.doc = '123456A'
> and (select count(1)
> from table1 b
> where a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party) > 1
If this worked it wouldreturn multiple rows of the same account number
>
How about:
SELECT a.account
FROM table1 a
JOIN table1 b ON a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party
WHERE a.doc = '123456A'
GROUP BY a.account
HAVING COUNT(*) > 1
> If I do the SELECT with out the sub select it works fine. Suggestions?
>
John
|||Reworking the statement worked around the issue.
=?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would be
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>
>If this worked it wouldreturn multiple rows of the same account number
>How about:
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>John
|||Hi Scott
"Scott Sheen" wrote:
> Reworking the statement worked around the issue.
>
Was this the statement I posted or something different? How many I/O is it
doing?
John
[TCP/IP Sockets]ConnectionCheckForData (CheckforData())
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionChe
ckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?Hi Scott
Having DDL and sample data with the expected results from that data would be
nice. See http://www.aspfaq.com/etiquette.asp?id=5006
"Scott Sheen" wrote:
> MS SQL 2000.
> When I attempt a SELECT I get the following:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionC
heckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> The offending SELECT
> select a.account
> from table1 a
> where a.doc = '123456A'
> and (select count(1)
> from table1 b
> where a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party) > 1
If this worked it wouldreturn multiple rows of the same account number
>
How about :
SELECT a.account
FROM table1 a
JOIN table1 b ON a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party
WHERE a.doc = '123456A'
GROUP BY a.account
HAVING COUNT(*) > 1
> If I do the SELECT with out the sub select it works fine. Suggestions?
>
John|||Reworking the statement worked around the issue.
examnotes <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would b
e
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>
>If this worked it wouldreturn multiple rows of the same account number
>
>How about :
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>John|||Hi Scott
"Scott Sheen" wrote:
> Reworking the statement worked around the issue.
>
Was this the statement I posted or something different? How many I/O is it
doing?
John
[TCP/IP Sockets]ConnectionCheckForData (CheckforData())
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?Reworking the statement worked around the issue.
=?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would be
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>> MS SQL 2000.
>> When I attempt a SELECT I get the following:
>> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
>> (CheckforData()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> Connection Broken
>>
>> The offending SELECT
>> select a.account
>> from table1 a
>> where a.doc = '123456A'
>> and (select count(1)
>> from table1 b
>> where a.account = b.account
>> and a.doc = b.doc
>> and a.oseq = b.oseq
>> and a.party = b.party) > 1
>If this worked it wouldreturn multiple rows of the same account number
>How about:
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>> If I do the SELECT with out the sub select it works fine. Suggestions?
>>
>Johnsql
Sunday, February 19, 2012
[DBNETLIB]ConnectionCheckForData (CheckforData())
SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
If i run this command on a remote server
select replicate(' ',190)
i have the following error
[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
if i run select replicate(' ',60) on the same server it completes
succesfully...
any ideas?...
thanks...Sangines (javier.sangines@.gruposenda.com) writes:
> SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
> If i run this command on a remote server
> select replicate(' ',190)
> i have the following error
> [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
> if i run select replicate(' ',60) on the same server it completes
> succesfully...
Interesting...
Often such events are accompnied by messages in the SQL Server errorlog
with a stack dump, indicating that there was an execution error in
SQL Server. However, given the statement you submit this sounds
unlikely. I assume that you run it from Query Analyzer?
So in this case, I would say that it smells a network problem of
some sort. Do you still get the message if you run the query locally
on the SQL Server machine? Do you get the message if you talk to
other SQL Servers?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||> Interesting...
> Often such events are accompnied by messages in the SQL Server errorlog
> with a stack dump, indicating that there was an execution error in
> SQL Server. However, given the statement you submit this sounds
> unlikely. I assume that you run it from Query Analyzer?
> So in this case, I would say that it smells a network problem of
> some sort. Do you still get the message if you run the query locally
> on the SQL Server machine? Do you get the message if you talk to
> other SQL Servers?
Thanks for quick response Erland...
Yes...it was a network problem, caused by misconfiguration in network device...
problem solved...
thanks again...