May 1, 2012 at 10:03 pm
I've found a way to avoid all performance problems associated with SSRS...
... avoid the use of SSRS. 😉
--Jeff Moden
July 9, 2012 at 12:32 pm
I have the exact same problem stored proc 19 second SSRS version unig same parameters 40 + minutes and still going. Anyone have a solution for this SSRS bug?
July 9, 2012 at 12:40 pm
You can check execution log for report and compare timerendering vs timedataretrieval. It could be poorly designed report that takes a lot of time to render.
September 6, 2012 at 9:14 am
@Dream, any resolution?
August 12, 2016 at 2:40 pm
Add the OPTION (OPTIMIZE FOR UNKNOWN)
August 14, 2016 at 9:56 am
dreamornightmare1 (7/9/2012)
I have the exact same problem stored proc 19 second SSRS version unig same parameters 40 + minutes and still going. Anyone have a solution for this SSRS bug?
Is your SSRS calling that same stored procedure or did you try to do it all in SSRS by itself?
--Jeff Moden
Viewing 6 posts - 31 through 35 (of 35 total)
You must be logged in to reply to this topic. Login to reply