I've set a report to run from cache and expire cache daily at 1:00 am. I've also set a caching schedule to produce caching for this report every day at 6 am. How can it be that when I first ran the report today at 10:00 am it took 13 seconds. Then after a couple of minutes from a different computer / session I ran it and it took only 4 seconds? What is the quickest way for the report to show for users? Is there any possibility to have it display immediately? ThanksNamnami

I would first start looking into a query that generates the report... If you run the query from the SSMS how long does it take? How much data does it return?Best Regards,Uri Dimant SQL Server MVP,http://sqlblog.com/blogs/uri_dimant/ Blog : MS SQL Development and Optimization Blog : Large scale of database and cleansing

Hi Namnami, Generally, the following factors cause a report cach to be expired: The report definition is modifiedReport parameters are modifiedData source credentials change Report execution options change If the parameter values that a user specifies to filter at 10:00 AM are different from those used to produce the cached report at 6:00 AM, the report cannot be rendered from the report cach and the report server will rerun the report. The report performance issue is always a complex issue. In Reporting Services, there are three processing phases when we view a report: data retrieve, report process and report rendering. When we execute the report either in Report Designer or on a report manager, the report rendering time may be different due to the rendering extension. To find out how many milliseconds of processing time is spent on each processing phase when we view a report on the report manager, you can view the report server execution log via the SSMS. For more information, please see: Report Server Execution Log and the ExecutionLog3 View Hope this helps. Regards, Mike YinMike Yin TechNet Community Support