Cached Report and Windows Authentication

I want to use cached reports with Reporting Services 2005. But when I edit the execution properties of a report, an error message answser that I can't use cache because it has a connexion to Analysis Services with Windows Authentication.

I understand why I can't do that, but I still want to do so, because the reports take too much time to load. How can I do that ?

Thanks.

You can configure the datasource in the report to run using stored credentials. In report manager, go the report and then click on the DataSource tab on the left side, you can store the credentials using that UI.|||

Thanks. I tried this and it works, but I don't see better performance...

I thought that I would not see "Generating Report, please wait" any more...

|||

Query the ExecutionLog table in the report server catalog database to see if we are submitting the queries. You can tell by looking at the "rowcount" column. You will also see how much time we are spending in processing and rendering respectively. Processing is the time that it takes for us to create the snapshot, and should be minimized by rendering from the execution cache.

|||

TimeDataRetrieval 645 0
TimeProcessing 4855 347
TimeRendering 23518 1090
Source 1 2
ByteCount 10249 10249
RowCount 183 21

Thank you, it seems that the cache is used. The first column is created the first time when the cache is generated, and the second column is created when I open the report a second time. I still got a RowCount > 0, I don't know why... Isn't there a way to tell the ReportServer the generate a .html file as cache, I think it would be much faster.

But then again, it works, so I thank you for your help.

|||We will automatically cache whatever we think is safe to cache. HTML caching can be problematic because there is some session specific information which is embedded in the HTML, so we cannot simply serve up the same HTML to multiple users.