Post reply

Finding a badly behaving/monopolising DB

  • January 10, 2008 at 5:53 pm

    #377911

    On one of my SQL 2000 servers my CPU is running at 99% almost constantly, the process behind it is the SQL server one.

    SO I can only assume that it is caused by some badly behaving DB as a result of inefficient queries.

    The problem is "how" to find this database?

    Any help would be appreciated.

    Thanks

  • January 10, 2008 at 7:49 pm

    #766948

    I would use SQL Profiler to check for queries that "take a while" to run. The "DUration" filter is what I would normally use as the first thing I use to find the cause of poor performance. I would start by getting all queries that take more than a 5 or 10 seconds. If you include the database id or database name in the list of columns returned by Profiler you should be able to find the database causing the problem fairly quickly.

  • January 10, 2008 at 8:10 pm

    #766950

    Do you have any detailed guide on this process possibly?

    Thanks

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

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