This is a multi-part message in MIME format.
--=_NextPart_000_0006_01C75217.31455020
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello!
I have been analyzing wait stats using get_waitstats_2005 on ou = production SQLserver (two node Active/Passive SQL Server 2005 64-bit = cluster) and noticed high values of
ASYNC_NETWORK_IO wait type (around 50% of total resource type). From = what I can see, our 1GB Network cards are all right. Has anyone had = experience troubleshooting this wait type? What could be causing high = percentage of this wait type?
Thanks,
Igor
--=_NextPart_000_0006_01C75217.31455020
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello!
I have been analyzing wait stats using get_waitstats_2005 on ou production SQLserver (two node Active/Passive = SQL Server 2005 64-bit cluster) and noticed high values of
ASYNC_NETWORK_IO wait type (around 50% of = total resource type). From what I can see, our 1GB Network cards are all = right. Has anyone had experience troubleshooting this wait type? What could be = causing high percentage of this wait type?
Thanks,
Igor
--=_NextPart_000_0006_01C75217.31455020--Hi
"imarchenko" wrote:
> Hello!
> I have been analyzing wait stats using get_waitstats_2005 on ou production SQLserver (two node Active/Passive SQL Server 2005 64-bit cluster) and noticed high values of
> ASYNC_NETWORK_IO wait type (around 50% of total resource type). From what I can see, our 1GB Network cards are all right. Has anyone had experience troubleshooting this wait type? What could be causing high percentage of this wait type?
> Thanks,
> Igor
50% of not very much is probably not something to worry about! If perfmon
stats such as output queue length show no problems then you are probably ok.
I assume that your 1GB network cards are on a 1GB network that does not have
any bottlenecks? If you can ad an extra card I don't think it would not do
any harm doing that!
John|||Also..
Have you checked for queries that return a large result set? You may want to
use SQL profiler to identify them. If you return an excessive result set the
client may not be able to process this fast enough!
John|||John,
This could well be the case. We have old legacy report application
generating thousands of queries per report.
Thanks,
Igor
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23z%23wpltUHHA.192@.TK2MSFTNGP04.phx.gbl...
> Also..
> Have you checked for queries that return a large result set? You may want
> to use SQL profiler to identify them. If you return an excessive result
> set the client may not be able to process this fast enough!
> John
>|||Hi Igor
"imarchenko" wrote:
> John,
> This could well be the case. We have old legacy report application
> generating thousands of queries per report.
> Thanks,
> Igor
Profiling the system will certainly show high I/O and duration queries. Look
for instances where the result set is too wide or too many rows are being
returned that are not being used.
If you can't tune or re-write the queries, maybe a different method of
delivery would be more approprate such as a scheduled report or DTS/SSIS
export. Use of Analysis Service may allow you to process your data in a more
piecemeal way?
John|||John,
AS is out of question at the moment, but we are working on improving this
app.
Thanks again,
Igor
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E11028-D4C0-4845-A347-03C5FEB1BE5D@.microsoft.com...
> Hi Igor
> "imarchenko" wrote:
>> John,
>> This could well be the case. We have old legacy report application
>> generating thousands of queries per report.
>> Thanks,
>> Igor
> Profiling the system will certainly show high I/O and duration queries.
> Look
> for instances where the result set is too wide or too many rows are being
> returned that are not being used.
> If you can't tune or re-write the queries, maybe a different method of
> delivery would be more approprate such as a scheduled report or DTS/SSIS
> export. Use of Analysis Service may allow you to process your data in a
> more
> piecemeal way?
> John
>
Friday, March 9, 2012
High ASYNC_NETWORK_IO value
Labels:
_nextpart_000_0006_01c75217,
async_network_io,
charset,
content-type,
database,
format,
iso-8859-1,
message,
microsoft,
mime,
multi-part,
mysql,
oracle,
plain,
server,
sql,
text,
value
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment