Post reply

Why the Delay in TimeStart

  • January 8, 2014 at 12:42 pm

    #280938

    I'm seeing some odd behavior in our SSRS 2008R2 environment. Our Reporting Services are running on a separate server from the database.

    The reports are starting significantly after the subscription time, and I need to know why to help prevent in the future. I am looking at historic data from 1st of the month reports, so it is not something I can easily recreate or monitor live.

    Per ReportServer.dbo.Subscriptions.LastRunTime = '2014-01-01 08:23:04.213'

    Per ReportServer.dbo.ExecutionLog.TimeStart = '2014-01-01 13:45:52.073'

    Notice this is nearly 5 hours delayed!!!

    The reports themselves run in about 1 minute (normal) generating xls files that are picked up by other external processes. Our users are complaining that when the reports generate so late, it throws off the later steps in the process and require a lot of manual cleanup (don't know/care these processes, just the loud complaints).

    If anyone can point me to what may be the cause of this lag, or where to query to find the info, I will be most grateful. SSRS logging has always struck me a cryptic at best, and nothing in the blogosphere has given me pointers yet.

  • January 8, 2014 at 1:11 pm

    #1678565

    The best way would be to write the reports to return the correct timeframe rather than relying on the time that they are executed.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 2 posts - 1 through 1 (of 1 total)

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