June 1, 2013 at 6:10 am
I'm working on a report that has a local query that just does a select from a table. The table is refreshed by stored procs that run at the beginning of the day and dump the latest changes into this table.
Recently, a user requested a change in a calculation performed in the stored procedure, and therein lies my issue...it seems that no matter what i do to change the stored procedure, the report keeps returning the same result, as if nothing has changed. When i breadboard the sproc in SSMS i can see the effect of the changes.
I remember hearing that SSRS caches results to speed execution and im wondering if this is the cause of seeing unchanged data on subsequent report executions.
Should i forget about the local query and invoke the stored procedure from the report?
Is there a way to disable the cache and force SSRS to go back to the server on every invocation?
i'll be bald soon
thanks a lot
drew
June 3, 2013 at 6:30 am
SSRS cache can be a curse and a blessing. It normally affects development as your making many changes quickly and end up being a victim of the cache's old data.
The only way you can "clear" the cache is to delete the .rdl.data file associated with the report. There is no other way to turn it off, disable, or refresh the cache.
June 3, 2013 at 10:20 pm
Holy good night!
it definitely has the potential to cause one to question their sanity...that's some freakin' feature!
Thanks a ton for the heads up
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply