SSRS Masters….
I’m having some trouble with SSRS custom screens refreshing. Basically, we want real time data but it’s taking about 10mins to update. This is only in the client though, when run in a browser it updates fine.
Under the report properties in SSRS report manager the following settings are selected:
Processing options: “Always run this report with the most recent data” and “Do not cache temporary copies of this report” are both checked.
Cache Refresh Options: there is nothing under this setting
I have even set both timeout options to 3 seconds (in T_DEFAULTS and in SSRS settings)
In the report server temp database there aren't any entries in the ExecutionCacheID table.
When I am working on the reports in visual studio I always delete the locally cached .data file if I want it to refresh – could it be that there are local data files being cached? If so, can I stop this?
Thanks for any advice,
Natasha
Natasha,
On the data source you are using in these reports, how are you passing credentials? Are you using a set of stored credentials?
Hi Ryan,
Thanks for your question, I just noticed that the data source uses the sa credentials, which is not such a great idea in itself. I will change this to our SSRS user, or, change the way we pass credentials altogether if it means real time data. Should credentials be set up differently for what I'm trying to achieve?
Thanks again,
Right, that's where I was going with the question. Storing credentials = caching potential.
From an article I found online (http://www.databasejournal.com/features/mssql/report-caching-in-sql-server-reporting-services-2008-r2.html):
Caching for a report can be enabled only if the report uses the data sources with stored credentials; in other words caching cannot be enabled for a report if it prompts users for credentials or uses Windows Integrated authentication.
So that would follow that if you need real-time data, you might want to try using Integrated authentication since prompting would be a pain for users. That may or may not be possible in your deployment.