Network I/O error in SQL 2000 ?

SQL 2000 with SP4 what causes a network I/O error which kept the data from
reaching the workstations?Hi
It is unlikely that this is a specific SP4 issue. You don't say whether this
is an intermitent or constant problem or exacly which error number and
message you are getting. You also don't say if this is happening on all
workstations and or the server.
So things to try: check the protocols that being used on server and client,
check for firewalls/virus checkers stopping the port/pipe, make sure that you
can ping/telnet the server, check the name is resolved correctly, check
timeouts...
John
"DGreg" wrote:
> SQL 2000 with SP4 what causes a network I/O error which kept the data from
> reaching the workstations?
>|||John
The error is related to the wait time and wait request on sql2000.
"John Bell" wrote:
> Hi
> It is unlikely that this is a specific SP4 issue. You don't say whether this
> is an intermitent or constant problem or exacly which error number and
> message you are getting. You also don't say if this is happening on all
> workstations and or the server.
> So things to try: check the protocols that being used on server and client,
> check for firewalls/virus checkers stopping the port/pipe, make sure that you
> can ping/telnet the server, check the name is resolved correctly, check
> timeouts...
> John
> "DGreg" wrote:
> > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > reaching the workstations?
> >|||Hi
Are you refering to DBCC SQLPERF? Changes were made regarding some of the
reporting such as latch waits but I don't know of anything that changed with
network I/O
John
"DGreg" wrote:
> John
> The error is related to the wait time and wait request on sql2000.
> "John Bell" wrote:
> > Hi
> >
> > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > is an intermitent or constant problem or exacly which error number and
> > message you are getting. You also don't say if this is happening on all
> > workstations and or the server.
> >
> > So things to try: check the protocols that being used on server and client,
> > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > can ping/telnet the server, check the name is resolved correctly, check
> > timeouts...
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > reaching the workstations?
> > >|||It relates to spid85 where I saw the network I/O ERROR.
"John Bell" wrote:
> Hi
> Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> reporting such as latch waits but I don't know of anything that changed with
> network I/O
> John
> "DGreg" wrote:
> > John
> >
> > The error is related to the wait time and wait request on sql2000.
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > is an intermitent or constant problem or exacly which error number and
> > > message you are getting. You also don't say if this is happening on all
> > > workstations and or the server.
> > >
> > > So things to try: check the protocols that being used on server and client,
> > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > can ping/telnet the server, check the name is resolved correctly, check
> > > timeouts...
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > reaching the workstations?
> > > >|||Hi
This will be a user connection, you may want to check the machine that is
was trying to connect.
John
"DGreg" wrote:
> It relates to spid85 where I saw the network I/O ERROR.
>
> "John Bell" wrote:
> > Hi
> >
> > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > reporting such as latch waits but I don't know of anything that changed with
> > network I/O
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > John
> > >
> > > The error is related to the wait time and wait request on sql2000.
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > is an intermitent or constant problem or exacly which error number and
> > > > message you are getting. You also don't say if this is happening on all
> > > > workstations and or the server.
> > > >
> > > > So things to try: check the protocols that being used on server and client,
> > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > timeouts...
> > > >
> > > > John
> > > >
> > > > "DGreg" wrote:
> > > >
> > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > reaching the workstations?
> > > > >|||Thanks John for the responses back, I'll have to look deeper into this.
Greg
"John Bell" wrote:
> Hi
> This will be a user connection, you may want to check the machine that is
> was trying to connect.
> John
> "DGreg" wrote:
> > It relates to spid85 where I saw the network I/O ERROR.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > reporting such as latch waits but I don't know of anything that changed with
> > > network I/O
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > John
> > > >
> > > > The error is related to the wait time and wait request on sql2000.
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > is an intermitent or constant problem or exacly which error number and
> > > > > message you are getting. You also don't say if this is happening on all
> > > > > workstations and or the server.
> > > > >
> > > > > So things to try: check the protocols that being used on server and client,
> > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > timeouts...
> > > > >
> > > > > John
> > > > >
> > > > > "DGreg" wrote:
> > > > >
> > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > reaching the workstations?
> > > > > >|||John,
What I'm experiencing is locked transactions. Intermittently, we experience
a transaction/process which will not complete. The process info display in
enterprise manager displays a "Wait Type" of Network I/O. Although, we do
expect to receive this type of message from time to time because of the
application not responding in a timely fashion, network collision, etc., the
process wait will usually either finish or remove itself from the list. The
problem comes forward when the "waiting" process never quits or otherwise
removes itself after any period of time (wait time continues to grow). This
results in subsequent transactions/processes waiting on this particular
error. Consequently, we experience a system wide data outage on the table
with the lock on it as no other processes can access it. We were under the
impression that this type of "latch" or "hang" was corrected in SP4, but
since it's raised it's head again with SP4 applied to the SQL instance, we
are worried about potential outages in the future. Please let me know if we
have any work arounds for these type of process "latches".
Sincerely,
DGreg
"DGreg" wrote:
> Thanks John for the responses back, I'll have to look deeper into this.
> Greg
>
> "John Bell" wrote:
> > Hi
> >
> > This will be a user connection, you may want to check the machine that is
> > was trying to connect.
> >
> > John
> >
> > "DGreg" wrote:
> >
> > > It relates to spid85 where I saw the network I/O ERROR.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > > reporting such as latch waits but I don't know of anything that changed with
> > > > network I/O
> > > >
> > > > John
> > > >
> > > > "DGreg" wrote:
> > > >
> > > > > John
> > > > >
> > > > > The error is related to the wait time and wait request on sql2000.
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > > is an intermitent or constant problem or exacly which error number and
> > > > > > message you are getting. You also don't say if this is happening on all
> > > > > > workstations and or the server.
> > > > > >
> > > > > > So things to try: check the protocols that being used on server and client,
> > > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > > timeouts...
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "DGreg" wrote:
> > > > > >
> > > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > > reaching the workstations?
> > > > > > >|||Hi
It is my understanding that SP4 improved the reporting of such problems
rather than curing them see http://support.microsoft.com/kb/906344 although I
believe that it is more to do with accessing data pages
http://support.microsoft.com/kb/822101/. Assuming that your lastwaittype is
NETWORKIO then you are waiting on the client to process your data. You may
want to look at what is happening on the client such as the specification of
the machine, also you may want to check if you are returning unnecessary
information such as result sets that are too wide, or procedures that should
be consolidated into one. Check out the scope of your transactions to see if
they can be made shorter and if there are unnecessary transactions, tuning
long running queries will also help. You also mentioned that you are seeing
network collissions, therefore this should be addressed.
John
"DGreg" wrote:
> John,
> What I'm experiencing is locked transactions. Intermittently, we experience
> a transaction/process which will not complete. The process info display in
> enterprise manager displays a "Wait Type" of Network I/O. Although, we do
> expect to receive this type of message from time to time because of the
> application not responding in a timely fashion, network collision, etc., the
> process wait will usually either finish or remove itself from the list. The
> problem comes forward when the "waiting" process never quits or otherwise
> removes itself after any period of time (wait time continues to grow). This
> results in subsequent transactions/processes waiting on this particular
> error. Consequently, we experience a system wide data outage on the table
> with the lock on it as no other processes can access it. We were under the
> impression that this type of "latch" or "hang" was corrected in SP4, but
> since it's raised it's head again with SP4 applied to the SQL instance, we
> are worried about potential outages in the future. Please let me know if we
> have any work arounds for these type of process "latches".
> Sincerely,
> DGreg
> "DGreg" wrote:
> > Thanks John for the responses back, I'll have to look deeper into this.
> >
> > Greg
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > This will be a user connection, you may want to check the machine that is
> > > was trying to connect.
> > >
> > > John
> > >
> > > "DGreg" wrote:
> > >
> > > > It relates to spid85 where I saw the network I/O ERROR.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > Are you refering to DBCC SQLPERF? Changes were made regarding some of the
> > > > > reporting such as latch waits but I don't know of anything that changed with
> > > > > network I/O
> > > > >
> > > > > John
> > > > >
> > > > > "DGreg" wrote:
> > > > >
> > > > > > John
> > > > > >
> > > > > > The error is related to the wait time and wait request on sql2000.
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > It is unlikely that this is a specific SP4 issue. You don't say whether this
> > > > > > > is an intermitent or constant problem or exacly which error number and
> > > > > > > message you are getting. You also don't say if this is happening on all
> > > > > > > workstations and or the server.
> > > > > > >
> > > > > > > So things to try: check the protocols that being used on server and client,
> > > > > > > check for firewalls/virus checkers stopping the port/pipe, make sure that you
> > > > > > > can ping/telnet the server, check the name is resolved correctly, check
> > > > > > > timeouts...
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "DGreg" wrote:
> > > > > > >
> > > > > > > > SQL 2000 with SP4 what causes a network I/O error which kept the data from
> > > > > > > > reaching the workstations?
> > > > > > > >