Post reply

Using much CPU and memore

  • June 11, 2008 at 12:34 am

    #381055

    Hi all,

    I am using MS sql server 2000. It is using much CPU and memory usage. I see this from task manager. The sqlservr is using the highest memory and CPU is always going more than 95%. I want to why it is going high ?

    I am not a DBA plz help me how to check which service is taking high %.

    Thanks

    gV

  • June 11, 2008 at 2:39 am

    #827114

    Is this a constant problem or does this happen only during certain time or is it kind of intermttent issue faced?

    Certain basic things you can check are:

    If there are any consistent blocks being noticed ( you can query sysprocesses table in Master DB or use SP_Who2).

    Check if there are any jobs (resource consuming) running when this (High CPU usage) happens

    Run the query "select * from master..sysprocesses order by cpu" and check the consistent SPIDs that are taking the high CPU time and use DBCC Inputbuffer(spid) to find out the last statement of that SPID.

    Are there any other monitoring jobs running continuously on the same server

    These are certain things that can be checked.....

    Renuka__

    [font="Verdana"]Renuka__[/font]

  • June 11, 2008 at 5:33 am

    #827164

    Hi Renuka,

    Thanks for great help, with a help my colleague i just went into MS SQL server and gave that query. In the bottom is displaying something as you asked me order by CPU. But what next i should do ? I have attached a .bmp file. Kindly have a look.

    Yes this happens everytime as you asked for. When i go to task manager and click process -->Memusage it give sqlservr is using almost 1,704,288 K.

    My CPU utilization is going to 90 % every 3 to 4 secs.

    Please look onto the snapshot let me knw what is to be done.

    I am running Reporter an HP Openview product. This is the product which uses this MS SQL server.

    I am running this on a Windows 2000 server, with 2 GB RAM and with 3 Ghz server.

    Thanks for ur help

    Gopalan V

  • June 11, 2008 at 6:33 am

    #827196

    Rather than simply spot checking by running sp_who2, you might consider setting up a trace to capture the stored procedures and query calls on the server over a period of time. Then you can identify which procedures are called most frequently or which ones take the most time, most cpu or all of the above.

    There are a bunch of articles that could help. Use the search box above. Here's one.[/url]

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply