dcsimg
Results 1 to 5 of 5

Thread: Where should the CPU Load be on a remote select from a database

  1. #1
    Join Date
    Aug 2015
    Posts
    2

    Where should the CPU Load be on a remote select from a database

    Searched for this answer but can't find anything, hopefully is not a duplicate.

    Where should the CPU load be ? For instance..

    I am remotely selecting results from a custom production database with a criteria of around three minutes from a C# application.

    Every time the select command is executed, the server PC that I am using CPU goes up to around 50%. But surely, the load should be on the database that I am connecting to?

    Why would the C# application rocket to 50% until the data is retrieved for reading?

    If any more info is needed please don't hesitate to ask!

    Thankyou

  2. #2
    Join Date
    Sep 2002
    Posts
    5,938
    Because client has to process rowset returned from sql server.

  3. #3
    Join Date
    Nov 2002
    Location
    New Jersey, USA
    Posts
    3,905
    You should limit the result set sent to client and try to use stored procedure to do most of the work on database server.

  4. #4
    Join Date
    Aug 2015
    Posts
    2
    Quote Originally Posted by rmiao View Post
    Because client has to process rowset returned from sql server.
    Sometimes there isn't a result set and it still has the same issue.

  5. #5
    Join Date
    Sep 2002
    Posts
    5,938
    Then you should check which process uses most cpu time in task manager.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •