Wednesday, March 28, 2012

How to make Report Caching work when rendering a report through the Web Services method Re

I've read carefully about the section "Report Caching in Reporting Services"
on the online document. It seems to me that report caching only works for
URL accesss. I use the web service method Render to render a report content,
and set cache option TimeExpiration.minutes = 20. However, each time when a
user make a Http request, the proxy object of ReportingService is recreated,
and it's Render method gets executed no matter whether the Cache option has
been set up or not. Is there any way that when I call the method "Render"
and tell this method to render from the cached report content instead of
reexecuting the report processing?It should automatically render from the cached report even in SOAP access.
You can test this by reading the SOAP header SessionHeader and checking the
IsNewExecution property. There is an example of this in Books Online. Seach
for SessionHeader.
--
Bryan Keller
Developer Documentation
SQL Server Reporting Services
A friendly reminder that this posting is provided "AS IS" with no
warranties, and confers no rights.
"Wendy H" <WendyH@.tequilasoftware.com> wrote in message
news:e7X9c$abEHA.212@.TK2MSFTNGP12.phx.gbl...
> I've read carefully about the section "Report Caching in Reporting
Services"
> on the online document. It seems to me that report caching only works for
> URL accesss. I use the web service method Render to render a report
content,
> and set cache option TimeExpiration.minutes = 20. However, each time when
a
> user make a Http request, the proxy object of ReportingService is
recreated,
> and it's Render method gets executed no matter whether the Cache option
has
> been set up or not. Is there any way that when I call the method "Render"
> and tell this method to render from the cached report content instead of
> reexecuting the report processing?
>|||I did something wrong, which reset cache option everytime when the render
method was called. After I move these codes into some other place, the
report caching works just as good as the one in Report Manager.
"Bryan Keller [MSFT]" <bryanke@.online.microsoft.com> wrote in message
news:eM6gh%23nbEHA.3988@.tk2msftngp13.phx.gbl...
> It should automatically render from the cached report even in SOAP access.
> You can test this by reading the SOAP header SessionHeader and checking
the
> IsNewExecution property. There is an example of this in Books Online.
Seach
> for SessionHeader.
> --
> Bryan Keller
> Developer Documentation
> SQL Server Reporting Services
> A friendly reminder that this posting is provided "AS IS" with no
> warranties, and confers no rights.
>
> "Wendy H" <WendyH@.tequilasoftware.com> wrote in message
> news:e7X9c$abEHA.212@.TK2MSFTNGP12.phx.gbl...
> > I've read carefully about the section "Report Caching in Reporting
> Services"
> > on the online document. It seems to me that report caching only works
for
> > URL accesss. I use the web service method Render to render a report
> content,
> > and set cache option TimeExpiration.minutes = 20. However, each time
when
> a
> > user make a Http request, the proxy object of ReportingService is
> recreated,
> > and it's Render method gets executed no matter whether the Cache option
> has
> > been set up or not. Is there any way that when I call the method
"Render"
> > and tell this method to render from the cached report content instead of
> > reexecuting the report processing?
> >
> >
>

No comments:

Post a Comment