Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2002
    Posts
    16

    Unanswered: SQL-Tracing with ASE 12.x

    Hi,
    Currently have an application which does not perform too well against ASE 12.x and it executes a lot of select and DML statements. I cannot seem to pin point the statement(s) which degrades the performance. Is there any tool (shareware or Sybase) which can help me figure out which statement(s) would cause the degradation. I am looking for something that would print the SQL statement being executed and the amount of CPU time taken on the execution of the statement.
    Any help would be appreciated.

    Thanks,
    Raghu.

  2. #2
    Join Date
    Feb 2002
    Location
    Willy is on vacation
    Posts
    1,208
    Hiya rajar11,

    BMC and Syabse have partnered to come out with an excellent Monitoring Tool called 'DB-Xray'.

    This is only available from ASE 12.5.0.3 onwards, as it needs some extra system tables implemented in that version. This product feeds off Monitor Server and is completely GUI driven with impressive graphs.

    Cheers
    Willy

  3. #3
    Join Date
    Aug 2002
    Location
    Madrid, Spain
    Posts
    97

    Re: SQL-Tracing with ASE 12.x

    Originally posted by rajar11
    Currently have an application which does not perform too well against ASE 12.x and it executes a lot of select and DML statements. I cannot seem to pin point the statement(s) which degrades the performance. Is there any tool (shareware or Sybase) which can help me figure out which statement(s) would cause the degradation. I am looking for something that would print the SQL statement being executed and the amount of CPU time taken on the execution of the statement.
    A poor but easy alternative is auditing. By
    auditing every SQL statement from a login
    (sp_audit cmdtext) you may collect the
    elapsed time between two consecutive
    SQL statements by subtracting their
    eventtime values.

    The limitations are two: the elapsed time
    covers SQL execution time, application
    logic time and ever user's think time.
    Some statements don't get traced, as
    cursor fetch.

    Regards,
    Mariano Corral

  4. #4
    Join Date
    Aug 2002
    Posts
    2
    Hi

    Two other methods come to my mind...

    1. use Sybase Open Switch and Turn trace on.
    All clients will be connected via Open Switch. Note that
    Open Switch des have some limitations.

    2. I think the best solution is to use a product called
    iWatch SQL from Exact-Solutions. Initial cost of
    getting product is well worth it for any installation.


    Goog Luck.

    Gajanan

Posting Permissions

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