December 10, 2007 at 1:13 pm
hi,
Here are some statistics for the executionlog table in the report server database for a single report - which failed at certain time. The report aborted since the processing time took more than the time out settings. That is clear to me. What I cannot understand is why the processing time is so long on the aborted attempts while the data retrieval is showing zero. The report just displays the result set from the execution of a stored procedure.
The first three columns represent data retrieval time, data processing time and rendering time.
375587403821rsSuccess
36249154251rsSuccess
675121rsSuccess
0184821401rsProcessingAborted
0183538101rsProcessingAborted
5403511rsSuccess
0180668601rsProcessingAborted
0184279001rsProcessingAborted
0184939601rsProcessingAborted
0184409001rsProcessingAborted
0183086101rsProcessingAborted
1907595161rsSuccess
469230171rsSuccess
22077161rsSuccess
98226273211rsSuccess
33422174241rsSuccess
555597885081rsSuccess
416426902661rsSuccess
622648635221rsSuccess
490266745261rsSuccess
Thanks
KR
December 10, 2007 at 1:16 pm
What is the report doing? Can you run Profiler and try to determine if this is a problem with the db engine or SSRS?
December 10, 2007 at 1:25 pm
The report is merely displaying the data from the stored procedure. It does have some company logos.
I could run the profiler, but I was wondering if someone could interpret the data from the executionlog first. If profiler is the only way to narrow down the cause of the issue then I guess I will have to do that first.
Thanks
Karthika
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply