Reporting Services SP1 Designer Cache Problem

Reporting Service SP1 provides an option to cache the data during
design time for preview, which seems to be making the preview to take
lot longer time than pre SP1.
This is what Reporting Services SP1 is doing:
During preview it is making a call to SQL and in between it is writing
into report data file, which is taking longer time just because it is
reading and writing into data file before even rendering.
Why can't it cache the data after it gets the entire data instead of
holding the sql connection or after rendering?
One of my reports is used to take 10 secs prior to SP1 now it is
taking 6 mins.
After turning of the configuration to false we started getting the
report in 10 secs.
Is there any resolution for this?
Thanks
RI have a couple of questions. Does this type of performance difference
occur for all reports or just this one? What is the structure of the data:
number of rows returned, etc. I would expect caching to take longer but not
in the magnitude you are describing.
The report is cached and rendered as we get the data (it is not buffered).
On the surface it seems quite in efficient to render the report and then
potentially round trip to the server again. Buffering is an issue since we
do not know the size of result set in advance.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"am_i_dotnet" <am_i_dotnet@.hotmail.com> wrote in message
news:ac7b2754.0407151240.2374c78b@.posting.google.com...
> Reporting Service SP1 provides an option to cache the data during
> design time for preview, which seems to be making the preview to take
> lot longer time than pre SP1.
> This is what Reporting Services SP1 is doing:
> During preview it is making a call to SQL and in between it is writing
> into report data file, which is taking longer time just because it is
> reading and writing into data file before even rendering.
> Why can't it cache the data after it gets the entire data instead of
> holding the sql connection or after rendering?
> One of my reports is used to take 10 secs prior to SP1 now it is
> taking 6 mins.
> After turning of the configuration to false we started getting the
> report in 10 secs.
> Is there any resolution for this?
> Thanks
> R|||There are around 20000+ records in this report and the report is in
tabular format.
I may not agree with you on "The report is cached and rendered as we
get the data". Because I observed the data file keep growing when I
tried to preview the report and report showed up only after the entire
data file created.
I know it is inefficient to make second round trip to server just to
cache the data but do we have any thoughts on using the data in the
report. I mean first render the report and cache the data
asynchronously from report data.
Thanks
R
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message news:<#dyED4qaEHA.3684@.TK2MSFTNGP09.phx.gbl>...
> I have a couple of questions. Does this type of performance difference
> occur for all reports or just this one? What is the structure of the data:
> number of rows returned, etc. I would expect caching to take longer but not
> in the magnitude you are describing.
> The report is cached and rendered as we get the data (it is not buffered).
> On the surface it seems quite in efficient to render the report and then
> potentially round trip to the server again. Buffering is an issue since we
> do not know the size of result set in advance.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "am_i_dotnet" <am_i_dotnet@.hotmail.com> wrote in message
> news:ac7b2754.0407151240.2374c78b@.posting.google.com...
> > Reporting Service SP1 provides an option to cache the data during
> > design time for preview, which seems to be making the preview to take
> > lot longer time than pre SP1.
> >
> > This is what Reporting Services SP1 is doing:
> > During preview it is making a call to SQL and in between it is writing
> > into report data file, which is taking longer time just because it is
> > reading and writing into data file before even rendering.
> >
> > Why can't it cache the data after it gets the entire data instead of
> > holding the sql connection or after rendering?
> >
> > One of my reports is used to take 10 secs prior to SP1 now it is
> > taking 6 mins.
> >
> > After turning of the configuration to false we started getting the
> > report in 10 secs.
> >
> > Is there any resolution for this?
> >
> > Thanks
> > R