BAD Current SQL quick remedy Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: BAD Current SQL quick remedy

  1. #1
    Join Date
    Nov 2000

    BAD Current SQL quick remedy

    what's the fastest way to capture top 5 most intesive running SQL and actulally make a PRACTICAL recommendation that what we have to do with thse?
    An ounce of prevention is worth a pound of cure

  2. #2
    Join Date
    Nov 2000
    Define "intensive". I/O intense, CPU intense, Latch Intense, etc.

    Simple, measure the metric that you say is "intense" and tune the query. If your query is using lots of CPU, figure out how to reduce it. If it's causing a lot of I/O, reduce it.
    Jeff Hunter
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

Posting Permissions

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

Click Here to Expand Forum to Full Width