Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Why the Delay in TimeStart Expand / Collapse
Author
Message
Posted Wednesday, January 8, 2014 12:42 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Yesterday @ 12:41 PM
Points: 6, Visits: 234
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.

Post #1529050
Posted Wednesday, January 8, 2014 1:11 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:27 AM
Points: 35,349, Visits: 31,889
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1529069
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse