SQL performance
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: SQL performance

  1. #1
    Join Date
    Dec 2001
    Posts
    6

    Post

    I would like to follow the performance of querys, and if some of them spend more then two hour and they could not finish yet I need to identify them and to kill.
    This procedure will avoid process running all day long because has some error or a SQL code miswrited.

  2. #2
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    So what kind of solutions are you looking for?

    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  3. #3
    Join Date
    Dec 2001
    Posts
    6

    Smile

    For exemple I would like to run a SQL to see if there are some SQL running more then two hour so I could open the source and analyse the code to clean mistakes.

  4. #4
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    go to sqlplus do
    set autotrace traceonly explain

    look the explain plan and you can get an idea of how good/bad will your SQL run, no timing information because it's not that smart yet without running the query

  5. #5
    Join Date
    Jul 2000
    Posts
    521
    A query running for two hours need not necessarily be bad.

    What you probably need to do is, schedule a job that will collect running SQLs and do explain plan on them. Examine these plans to decide what is bad what is not.
    svk

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