Hi,
There is an application which makes connection of more than 300 users
to a SQL Server 2000 DB.
Most of the times the server CPU hits the 100% for 2-3 seconds.
Since lots of queries are fired hence i'm unable to track down which
query makes the CPU 100%.
I'm using the SQL profiler (with settings on the Duration filter),
still i'm unabl;e to track down the BAD Queries.
Please suggest me a way/method/application to TRACK DOWN THE QUERIES
RESPONSIBLE TO OVERLOAD THE CPU BY 100 %.
Thanks,
~Nimit Sharma.Hi
Turn on SQL Server Profiler and filter by CPU
<nimitsharma16@.gmail.com> wrote in message
news:1189330367.686296.120070@.19g2000hsx.googlegroups.com...
> Hi,
> There is an application which makes connection of more than 300 users
> to a SQL Server 2000 DB.
> Most of the times the server CPU hits the 100% for 2-3 seconds.
> Since lots of queries are fired hence i'm unable to track down which
> query makes the CPU 100%.
> I'm using the SQL profiler (with settings on the Duration filter),
> still i'm unabl;e to track down the BAD Queries.
> Please suggest me a way/method/application to TRACK DOWN THE QUERIES
> RESPONSIBLE TO OVERLOAD THE CPU BY 100 %.
> Thanks,
> ~Nimit Sharma.
>|||Generally, it a normal behavior when some query utilizie 100% of CPU for 2-3
seconds, specially if it is using the data that are already in cache. Do you
really need to track such queries?
"nimitsharma16@.gmail.com" wrote:
> Hi,
> There is an application which makes connection of more than 300 users
> to a SQL Server 2000 DB.
> Most of the times the server CPU hits the 100% for 2-3 seconds.
> Since lots of queries are fired hence i'm unable to track down which
> query makes the CPU 100%.
> I'm using the SQL profiler (with settings on the Duration filter),
> still i'm unabl;e to track down the BAD Queries.
> Please suggest me a way/method/application to TRACK DOWN THE QUERIES
> RESPONSIBLE TO OVERLOAD THE CPU BY 100 %.
> Thanks,
> ~Nimit Sharma.
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment