Advice on where to look.

  • Hi,

    I have an issue at a customer site where our application is reportedly running slow. I have a trace but the top duration event in the trace is:

    set implicit transactions on

    Now normally we would see a select/insert/update/delete statement and would then look at the code to resolve the issue. But we are a bit stumped at why the above statement would have the highest duration.

    For completeness the second and third highest duration calls where:

    if @@trancount > {##} commit tran

    if @@trancount > {##} commit tran set implicit transaction off

    Thanks

    Ronnie

  • What events are you using in your trace and are you filtering it, and if so by what

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

  • Hi,

    I analyze the traces using the RML Utility, and we have a standard trace template we use for our application. It is just this is the first time these statements have been seen as the highest duration. The normal select etc statements are there but not at as high a duration.

    Thanks

    Ronnie

  • If you have direct access to the server, have you looked at any of the DMV's like sys.dm_exec_query_stats?

  • What is the Avg Queue length on the log disk?

    Regards

    Piotr

    ...and your only reply is slàinte mhath

  • Hi,

    We will investigate the queue length.

    Thanks

    Ronnie

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply