Excessive cpu utilisation on sql server 2000

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Akhila John
    New Member
    • Apr 2013
    • 2
    #1

    Excessive cpu utilisation on sql server 2000

    SQL server is runing at 80% of CPU utilization. There are some issues with the front end application that connects to this server.
    1.Application fault - a database browse is retrieving all records from a table, rather than a subset
    2.Archiving – data is not being archived so building up, presumably exacerbating issue 1).

    will this be a reason for high CPU usage.

    I dont have access to this server. But i'm asked to resolve this issue as i'm i maitanence of this application. So I need to provide instructions to DBA.Could you please advise me on this.
    Tags: None
    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32654
      #2
      There are 101 possible causes for this, but to determine which are involved you need to see what's going on. Asking for an answer without being able to see the question is not much more clever from you here, than it is for whomever suggested you advise the DBA without access to the information.

        Comment

        • Akhila John
          New Member
          • Apr 2013
          • 2
          #3
          Thanks for your response. I got the result of sp_who2 when the CPU usage was high. In that I could find that three IIS servers are connected to the server and the the SQL server is awaiting command for a long time from each IIS servers.will this be a reason for the high CPU usage.
          Please find the below commands and CPU usage

          AWAITING COMMAND 274085 69 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 95907 53 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 365109 19 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 21787 84 01/04/1930 14:11 .Net SqlClient Data Provider
          AWAITING COMMAND 348497 2 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 2078 6 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 14015 43 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 33188 74 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 32699 92 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 277989 57 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 150040 31 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 23572 251 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 2766 3 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 314415 58 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 22452 19 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 97235 1 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 94946 14 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 18706 80 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 361641 11 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 12870 24 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 368927 9 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 451772 10 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 172999 58 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 75163 6 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 4384 16 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 7438 20 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 526370 1 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 87026 25 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 103462 36 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 12846 27 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 17663 29 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 24627 34 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 4274 35 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 185793 3 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 666134 38 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 5099 6 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 1421 0 01/04/1930 14:12 .Net SqlClient Data Provider
          AWAITING COMMAND 297037 14 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 14164 27 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 2047 3 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 346555 51 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 22221 0 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 556153 60 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 91547 1 01/04/1930 14:13 .Net SqlClient Data Provider
          AWAITING COMMAND 97634 1 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 19068 22 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 102515 18 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 8329 13 01/04/1930 14:14 .Net SqlClient Data Provider
          AWAITING COMMAND 1906 0 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 199915 88 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 689 0 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 2313 0 01/04/1930 14:15 .Net SqlClient Data Provider
          AWAITING COMMAND 106524 28 01/04/1930 14:15 .Net SqlClient Data Provider

            Comment

            • NeoPa
              Recognized Expert Moderator MVP
              • Oct 2006
              • 32654
              #4
              I can't be absolutely positive, but this indicates to me that you have a number of threads taking up resources, but which are fundamentally not busy doing any work. As long as you're not running short of resources on your server I see no cause for delays from this quarter.

                Comment

                Previous template Next
                Working...