n/w issues and had to reboot.

Has anyone sees issues where although the exec plans are the same , theres
no blocking, and identical hardware that the query would perform slower at
times to return the results to the client whereas it runs much faster when
run on the same box. The query return a few million rows.. It takes as long
as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
results on the client.
Even stopping and starting SQL doesnt work. I just have to reboot and then
its all fast again. I am thinking its being choked someplace.
I have seen this same behaviour on another server as well. and only a reboot
would work. No messages in the log, nothing..
A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
Try sp_updatestats
I had simillar problem, VB6 client ran very slow sometimes, but the same
query (meanwhile!) ran fast in QA.
tv
Hassan napsal(a):
> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as long
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a reboot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>
|||Have your done profiling and perf-mon'ing of the boxes during these phases?
What are your cache hit ratio's like? Are you suffereing from disk IO queue's
going excessive? Are you having excessive paging? What does CPU utilization
look like?
When it takes 5 minutes, is it after a few iterations (i.e. data has been
cached by previous runs), etc.
"Hassan" wrote:

> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as long
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a reboot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>
|||Even a restart of SQL Service wont help.. But a reboot of a server sure
does fix it
"Wanderer" <Wanderer@.discussions.microsoft.com> wrote in message
news:957C21BB-A9EE-4E33-8903-205053E55821@.microsoft.com...
> Have your done profiling and perf-mon'ing of the boxes during these
phases?
> What are your cache hit ratio's like? Are you suffereing from disk IO
queue's
> going excessive? Are you having excessive paging? What does CPU
utilization[vbcol=seagreen]
> look like?
> When it takes 5 minutes, is it after a few iterations (i.e. data has been
> cached by previous runs), etc.
> "Hassan" wrote:
theres[vbcol=seagreen]
at[vbcol=seagreen]
when[vbcol=seagreen]
long[vbcol=seagreen]
these[vbcol=seagreen]
then[vbcol=seagreen]
reboot[vbcol=seagreen]

n/w issues and had to reboot.

Has anyone sees issues where although the exec plans are the same , theres
no blocking, and identical hardware that the query would perform slower at
times to return the results to the client whereas it runs much faster when
run on the same box. The query return a few million rows.. It takes as long
as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
results on the client.
Even stopping and starting SQL doesnt work. I just have to reboot and then
its all fast again. I am thinking its being choked someplace.
I have seen this same behaviour on another server as well. and only a reboot
would work. No messages in the log, nothing..
A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003Try sp_updatestats
I had simillar problem, VB6 client ran very slow sometimes, but the same
query (meanwhile!) ran fast in QA.
tv
Hassan napsal(a):
> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as lon
g
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain thes
e
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a rebo
ot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>|||Have your done profiling and perf-mon'ing of the boxes during these phases?
What are your cache hit ratio's like? Are you suffereing from disk IO queue'
s
going excessive? Are you having excessive paging? What does CPU utilization
look like?
When it takes 5 minutes, is it after a few iterations (i.e. data has been
cached by previous runs), etc.
"Hassan" wrote:

> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as lon
g
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain thes
e
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a rebo
ot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>|||Even a restart of SQL Service wont help.. But a reboot of a server sure
does fix it
"Wanderer" <Wanderer@.discussions.microsoft.com> wrote in message
news:957C21BB-A9EE-4E33-8903-205053E55821@.microsoft.com...
> Have your done profiling and perf-mon'ing of the boxes during these
phases?
> What are your cache hit ratio's like? Are you suffereing from disk IO
queue's
> going excessive? Are you having excessive paging? What does CPU
utilization[vbcol=seagreen]
> look like?
> When it takes 5 minutes, is it after a few iterations (i.e. data has been
> cached by previous runs), etc.
> "Hassan" wrote:
>
theres[vbcol=seagreen]
at[vbcol=seagreen]
when[vbcol=seagreen]
long[vbcol=seagreen]
these[vbcol=seagreen]
then[vbcol=seagreen]
reboot[vbcol=seagreen]

n/w issues and had to reboot.

Has anyone sees issues where although the exec plans are the same , theres
no blocking, and identical hardware that the query would perform slower at
times to return the results to the client whereas it runs much faster when
run on the same box. The query return a few million rows.. It takes as long
as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
results on the client.
Even stopping and starting SQL doesnt work. I just have to reboot and then
its all fast again. I am thinking its being choked someplace.
I have seen this same behaviour on another server as well. and only a reboot
would work. No messages in the log, nothing..
A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003Try sp_updatestats
I had simillar problem, VB6 client ran very slow sometimes, but the same
query (meanwhile!) ran fast in QA.
tv
Hassan napsal(a):
> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as long
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a reboot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>|||Have your done profiling and perf-mon'ing of the boxes during these phases?
What are your cache hit ratio's like? Are you suffereing from disk IO queue's
going excessive? Are you having excessive paging? What does CPU utilization
look like?
When it takes 5 minutes, is it after a few iterations (i.e. data has been
cached by previous runs), etc.
"Hassan" wrote:
> Has anyone sees issues where although the exec plans are the same , theres
> no blocking, and identical hardware that the query would perform slower at
> times to return the results to the client whereas it runs much faster when
> run on the same box. The query return a few million rows.. It takes as long
> as 1 hr when its slow and as fast as 5 mins when its normal to obtain these
> results on the client.
> Even stopping and starting SQL doesnt work. I just have to reboot and then
> its all fast again. I am thinking its being choked someplace.
> I have seen this same behaviour on another server as well. and only a reboot
> would work. No messages in the log, nothing..
> A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
>
>|||Even a restart of SQL Service wont help.. But a reboot of a server sure
does fix it
"Wanderer" <Wanderer@.discussions.microsoft.com> wrote in message
news:957C21BB-A9EE-4E33-8903-205053E55821@.microsoft.com...
> Have your done profiling and perf-mon'ing of the boxes during these
phases?
> What are your cache hit ratio's like? Are you suffereing from disk IO
queue's
> going excessive? Are you having excessive paging? What does CPU
utilization
> look like?
> When it takes 5 minutes, is it after a few iterations (i.e. data has been
> cached by previous runs), etc.
> "Hassan" wrote:
> > Has anyone sees issues where although the exec plans are the same ,
theres
> > no blocking, and identical hardware that the query would perform slower
at
> > times to return the results to the client whereas it runs much faster
when
> > run on the same box. The query return a few million rows.. It takes as
long
> > as 1 hr when its slow and as fast as 5 mins when its normal to obtain
these
> > results on the client.
> >
> > Even stopping and starting SQL doesnt work. I just have to reboot and
then
> > its all fast again. I am thinking its being choked someplace.
> > I have seen this same behaviour on another server as well. and only a
reboot
> > would work. No messages in the log, nothing..
> >
> > A reboot always solves it. Any idea why.. Using SQL 2000 on Windows 2003
> >
> >
> >
> >sql

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.
Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.co...prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.com/sf_block_prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.c..._prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>