report run time

Last Post 10 Aug 2011 08:39 AM by rm. 4 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
dbandee
New Member
New Member

--
10 Aug 2011 05:26 AM

Good morning
I have huge report that runs abuot 30 secs in dev but 5 min in production
sproc runs 15 secs in ssms in both environments.
ssrs settings are the same on both boxes,

any thoughts?

thank you

gunneyk
New Member
New Member

--
10 Aug 2011 05:50 AM
Are you saying that the sproc is what the report is running? If the sproc runs in 15 seconds in production with the same exact parameters that SSRS calls it with I would suspect either the server that SSRS is running on is under powered or overloaded. Second I would check the network between the two boxes. Do you have SSMS on the reporting services box? If so how long does the proc take to run that way?
dbandee
New Member
New Member

--
10 Aug 2011 07:26 AM

thank for the reply
its all on the same box
when i run sproc locally on the box in ssms query window it completes in abuot 13-15 seconds.

execution plan and time are the same as on test server

dbandee
New Member
New Member

--
10 Aug 2011 08:11 AM

mystery solved

There is a setting in ssrs:

Enable report Execution Logging

i had it set to 360 which is not a valid value

i know it because when you look at ssrs setting in ssms (you have to connect to ssrs in ssms) i was getting error 360 is not a valid value. however i was ablt to enter te value through IE and was not getting the error 9 i guess micorosft has to fix it)

so i suspect report execution was hangin on logging and then after it timed out it would run the actual report. because in profiler i could see report hang right on the last select

So i changed it to 60 and everything work great now. report runs even faster then in dev

hope this helps

i am going to lunch now

rm
New Member
New Member

--
10 Aug 2011 08:39 AM
Good to know, thanks for sharing.
You are not authorized to post a reply.

Acceptable Use Policy