Report Does Not Render!

Hello,
I am trying to get my report to render on the Report Server, but it
fails to do so. I am able to see that the report is generating, but
after a period of 30 or more minutes, the same image is displayed on
the screen. I know, for sure, that the query that is grabbing the data
takes about 10 minutes. What could be the problem? I have increased
the timeouts in every place possible: IIS, Report Manager, the data
source. Am I missing something? Please help! Thanks!
-MichaelHow many rows of data are being returned? Are you using filters or query
parameters? How is it being rendered (the default is html)? Or are you
specifying PDF?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<mjhaddad@.gmail.com> wrote in message
news:1119397987.766833.119040@.f14g2000cwb.googlegroups.com...
> Hello,
> I am trying to get my report to render on the Report Server, but it
> fails to do so. I am able to see that the report is generating, but
> after a period of 30 or more minutes, the same image is displayed on
> the screen. I know, for sure, that the query that is grabbing the data
> takes about 10 minutes. What could be the problem? I have increased
> the timeouts in every place possible: IIS, Report Manager, the data
> source. Am I missing something? Please help! Thanks!
> -Michael
>|||Bruce,
Thanks for your reply. Originally I was returning 10,000 rows of data,
but I have limited it to 100 rows. I am using 4 query parameters: a
start date, an end date, sort by, and hotel property. It is being
rendered by the default, HTML. I also want to mention that the report
does show up when the query execution time is around 3 minutes or so.
Thank you for your help!|||Michael:
Have you received any further feedback on this? I am experiencing a similar
issue when i have a report that returns about 10,000 rows. With less rows
and a quicker query execution (6 minutes or less) the report comes back.
-Jeff
"Michael" wrote:
> Bruce,
> Thanks for your reply. Originally I was returning 10,000 rows of data,
> but I have limited it to 100 rows. I am using 4 query parameters: a
> start date, an end date, sort by, and hotel property. It is being
> rendered by the default, HTML. I also want to mention that the report
> does show up when the query execution time is around 3 minutes or so.
> Thank you for your help!
>|||RS renders in RAM. How much data it handles without major slowdown depends
on the format. 10,000 rows is not something for a human to look at. That
much data in my mind is a data export to another program (like Excel).
Rendering to HTML and to CSV format is very fast and can handle much larger
datasets without a massive slowdown. PDF and Excel export really slows down.
The default CSV export is Unicode that Excel doesn't handle well. Use jump
to URL and render as ASCII CSV. Very very fast and I have done 60,000 rows
that way.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JeffW" <JeffW@.discussions.microsoft.com> wrote in message
news:1E215FB6-73A5-483C-9744-600ACA0D37F0@.microsoft.com...
> Michael:
> Have you received any further feedback on this? I am experiencing a
> similar
> issue when i have a report that returns about 10,000 rows. With less rows
> and a quicker query execution (6 minutes or less) the report comes back.
> -Jeff
> "Michael" wrote:
>> Bruce,
>> Thanks for your reply. Originally I was returning 10,000 rows of data,
>> but I have limited it to 100 rows. I am using 4 query parameters: a
>> start date, an end date, sort by, and hotel property. It is being
>> rendered by the default, HTML. I also want to mention that the report
>> does show up when the query execution time is around 3 minutes or so.
>> Thank you for your help!
>>|||Thanks for the prompt follow up Bruce.
Your point about the amount of data a human might look at is well taken. I
may need to revisit my SQL, as the report i am working with takes the 10,00
rows and transposes them into 15-20 columns of data. So, I really only end
up with a couple hundred rows by 15-20 columns. I've tried using matrix
style reporting for this, but could never really get all the formatting quite
right as i can with just a table style report. I may need to get the data
coming back to resemble the report a bit more closely so RS doesn't need to
do so much processing.
The only odd part is that when i watch the aspnet_wp on the report server as
the db server finsihes up it's query, the worker process does not start
gobbling up memory. It grabs a chunk of cpu for a few seconds, but barely
budges on memory. in the past, i have had exports where the wp maxes out the
memory (1.5 gig of RAM ro so) and then i get the RS out of memory error. For
the report i was originally referring to in this post, this never happens.
Instead, the report just never comes back. It's as if RS never even tried to
return the report.
Also, i did not know that about the csv export. i will begin using that
immediately so thank you for that tip.
-JeffW
"Bruce L-C [MVP]" wrote:
> RS renders in RAM. How much data it handles without major slowdown depends
> on the format. 10,000 rows is not something for a human to look at. That
> much data in my mind is a data export to another program (like Excel).
> Rendering to HTML and to CSV format is very fast and can handle much larger
> datasets without a massive slowdown. PDF and Excel export really slows down.
> The default CSV export is Unicode that Excel doesn't handle well. Use jump
> to URL and render as ASCII CSV. Very very fast and I have done 60,000 rows
> that way.
> Here is an example of a Jump to URL link I use. This causes Excel to come up
> with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "JeffW" <JeffW@.discussions.microsoft.com> wrote in message
> news:1E215FB6-73A5-483C-9744-600ACA0D37F0@.microsoft.com...
> > Michael:
> >
> > Have you received any further feedback on this? I am experiencing a
> > similar
> > issue when i have a report that returns about 10,000 rows. With less rows
> > and a quicker query execution (6 minutes or less) the report comes back.
> >
> > -Jeff
> >
> > "Michael" wrote:
> >
> >> Bruce,
> >>
> >> Thanks for your reply. Originally I was returning 10,000 rows of data,
> >> but I have limited it to 100 rows. I am using 4 query parameters: a
> >> start date, an end date, sort by, and hotel property. It is being
> >> rendered by the default, HTML. I also want to mention that the report
> >> does show up when the query execution time is around 3 minutes or so.
> >> Thank you for your help!
> >>
> >>
>
>|||Thanks to Bruce and Jeff for the replies, but I am still unsure what to
do to solve my issue. I am only returning 100 rows and the report is
not displaying. In the ReportServer database and in the ExecutionLog,
it shows that the report has completed execution, but there is no
report displaying. What is going on? Please help! Thanks!|||Does it work from the development environment? Where are you displaying this
report, i.e. from your own web page or from Report Manager? If from your own
web page then does the report work from Report Manager?
100 rows should definitely work.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael" <mjhaddad@.gmail.com> wrote in message
news:1119472105.958590.53550@.g44g2000cwa.googlegroups.com...
> Thanks to Bruce and Jeff for the replies, but I am still unsure what to
> do to solve my issue. I am only returning 100 rows and the report is
> not displaying. In the ReportServer database and in the ExecutionLog,
> it shows that the report has completed execution, but there is no
> report displaying. What is going on? Please help! Thanks!
>|||Bruce, it does preview fine in VS .NET. I have deployed the report to
the ReportServer and then try to run it and nothing happens. The same
thing occurs in the ReportManager. Let me know what you think. Thanks!|||Check your credentials datasource for the report.
How fast does it return from the development environment?
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael" <mjhaddad@.gmail.com> wrote in message
news:1119473999.367244.23380@.o13g2000cwo.googlegroups.com...
> Bruce, it does preview fine in VS .NET. I have deployed the report to
> the ReportServer and then try to run it and nothing happens. The same
> thing occurs in the ReportManager. Let me know what you think. Thanks!
>|||Bruce, credentials are fine and the report returns in a little over 10
minutes from the development environment.|||100 rows should not be a problem. Plus you say that if the report comes back
in 3 minutes you are OK. This makes me think that it is an IIS issue. That
IIS is timing out on you. I have heard of people adjusting something in IIS
for this but I am not sure where it is done.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael" <mjhaddad@.gmail.com> wrote in message
news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
> Bruce, credentials are fine and the report returns in a little over 10
> minutes from the development environment.
>|||Bruce, I have adjusted the time out for IIS, but it did not resolve the
issue. I am lost, to be honest with you. Thanks for your help!|||Hi Bruce,
I have a similar issue but much more data on a server with 3G memory. I use
RS to render 200,000 rows to CSV and thought that would be better than PDF,
but it took more than 30 minutes and then threw OutOfMemory exeception and RS
got restarted many times according to Event log. We already raise MaxMemory
to 120 in the config file, but just don't know why RS still can not render a
csv file. We really need to render that much data into a report for clients.
Does anyone know how to use RS deal with that much amount of data? Is there
some other way I can try? Thank you.
Charles
"Bruce L-C [MVP]" wrote:
> 100 rows should not be a problem. Plus you say that if the report comes back
> in 3 minutes you are OK. This makes me think that it is an IIS issue. That
> IIS is timing out on you. I have heard of people adjusting something in IIS
> for this but I am not sure where it is done.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Michael" <mjhaddad@.gmail.com> wrote in message
> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
> > Bruce, credentials are fine and the report returns in a little over 10
> > minutes from the development environment.
> >
>
>|||Michael,
Try to adjust to MaxMemory in RS config file(default is 60) and that may help.
Charles
"Michael" wrote:
> Bruce, I have adjusted the time out for IIS, but it did not resolve the
> issue. I am lost, to be honest with you. Thanks for your help!
>|||I have done about 60,000 rows but they were small (very few columns).
200,000 is just past what RS is designed for. My suggestion is to look at
other technologies to do this (like DTS etc).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
> Hi Bruce,
> I have a similar issue but much more data on a server with 3G memory. I
> use
> RS to render 200,000 rows to CSV and thought that would be better than
> PDF,
> but it took more than 30 minutes and then threw OutOfMemory exeception and
> RS
> got restarted many times according to Event log. We already raise
> MaxMemory
> to 120 in the config file, but just don't know why RS still can not render
> a
> csv file. We really need to render that much data into a report for
> clients.
> Does anyone know how to use RS deal with that much amount of data? Is
> there
> some other way I can try? Thank you.
> Charles
> "Bruce L-C [MVP]" wrote:
>> 100 rows should not be a problem. Plus you say that if the report comes
>> back
>> in 3 minutes you are OK. This makes me think that it is an IIS issue.
>> That
>> IIS is timing out on you. I have heard of people adjusting something in
>> IIS
>> for this but I am not sure where it is done.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Michael" <mjhaddad@.gmail.com> wrote in message
>> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
>> > Bruce, credentials are fine and the report returns in a little over 10
>> > minutes from the development environment.
>> >
>>|||Hi Bruce,
Thanks for your reply. Is there any document that mentions about report
render limit for each report format (csv, pdf,...)? Thanks.
Charles
"Bruce L-C [MVP]" wrote:
> I have done about 60,000 rows but they were small (very few columns).
> 200,000 is just past what RS is designed for. My suggestion is to look at
> other technologies to do this (like DTS etc).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
> > Hi Bruce,
> >
> > I have a similar issue but much more data on a server with 3G memory. I
> > use
> > RS to render 200,000 rows to CSV and thought that would be better than
> > PDF,
> > but it took more than 30 minutes and then threw OutOfMemory exeception and
> > RS
> > got restarted many times according to Event log. We already raise
> > MaxMemory
> > to 120 in the config file, but just don't know why RS still can not render
> > a
> > csv file. We really need to render that much data into a report for
> > clients.
> > Does anyone know how to use RS deal with that much amount of data? Is
> > there
> > some other way I can try? Thank you.
> >
> > Charles
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> 100 rows should not be a problem. Plus you say that if the report comes
> >> back
> >> in 3 minutes you are OK. This makes me think that it is an IIS issue.
> >> That
> >> IIS is timing out on you. I have heard of people adjusting something in
> >> IIS
> >> for this but I am not sure where it is done.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Michael" <mjhaddad@.gmail.com> wrote in message
> >> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
> >> > Bruce, credentials are fine and the report returns in a little over 10
> >> > minutes from the development environment.
> >> >
> >>
> >>
> >>
>
>|||No, there is not a document. I'm sure it varies depending on the RAM you
have and other configuration issues. In general though I would say the
product is designed around human consumption not data loads. Sometimes a
relatively large amount of data is for use by a person for instance into
Excel. Until recently Excel had a limit of 64,000 which when doing CSV RS
can handle (at least on my box which has 2 gigs of RAM). One thing you might
want to try is to see if the user needs all the columns of the report when
you export to CSV. If not, then you could have an alternate report just for
that. What I do sometimes is have a report for viewing and a report to
exporting. I hide the exporting one in list view and then I add a link with
a jump to URL at the top of the report. It exports in CSV ASCII (very
important, default by RS is Unicode which Excel does not recognize).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:C9BBC97A-7E32-4241-ABF5-177FFA654E04@.microsoft.com...
> Hi Bruce,
> Thanks for your reply. Is there any document that mentions about report
> render limit for each report format (csv, pdf,...)? Thanks.
>
> Charles
> "Bruce L-C [MVP]" wrote:
>> I have done about 60,000 rows but they were small (very few columns).
>> 200,000 is just past what RS is designed for. My suggestion is to look at
>> other technologies to do this (like DTS etc).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
>> news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
>> > Hi Bruce,
>> >
>> > I have a similar issue but much more data on a server with 3G memory. I
>> > use
>> > RS to render 200,000 rows to CSV and thought that would be better than
>> > PDF,
>> > but it took more than 30 minutes and then threw OutOfMemory exeception
>> > and
>> > RS
>> > got restarted many times according to Event log. We already raise
>> > MaxMemory
>> > to 120 in the config file, but just don't know why RS still can not
>> > render
>> > a
>> > csv file. We really need to render that much data into a report for
>> > clients.
>> > Does anyone know how to use RS deal with that much amount of data? Is
>> > there
>> > some other way I can try? Thank you.
>> >
>> > Charles
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> 100 rows should not be a problem. Plus you say that if the report
>> >> comes
>> >> back
>> >> in 3 minutes you are OK. This makes me think that it is an IIS issue.
>> >> That
>> >> IIS is timing out on you. I have heard of people adjusting something
>> >> in
>> >> IIS
>> >> for this but I am not sure where it is done.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Michael" <mjhaddad@.gmail.com> wrote in message
>> >> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
>> >> > Bruce, credentials are fine and the report returns in a little over
>> >> > 10
>> >> > minutes from the development environment.
>> >> >
>> >>
>> >>
>> >>
>>|||Hi Bruce,
Currently I use data driven subscription to render CSV file. How do I render
CSV in ASCII from the subscription? Would it be faster and less memory
intensive? Thanks.
Charles
"Bruce L-C [MVP]" wrote:
> No, there is not a document. I'm sure it varies depending on the RAM you
> have and other configuration issues. In general though I would say the
> product is designed around human consumption not data loads. Sometimes a
> relatively large amount of data is for use by a person for instance into
> Excel. Until recently Excel had a limit of 64,000 which when doing CSV RS
> can handle (at least on my box which has 2 gigs of RAM). One thing you might
> want to try is to see if the user needs all the columns of the report when
> you export to CSV. If not, then you could have an alternate report just for
> that. What I do sometimes is have a report for viewing and a report to
> exporting. I hide the exporting one in list view and then I add a link with
> a jump to URL at the top of the report. It exports in CSV ASCII (very
> important, default by RS is Unicode which Excel does not recognize).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> news:C9BBC97A-7E32-4241-ABF5-177FFA654E04@.microsoft.com...
> > Hi Bruce,
> >
> > Thanks for your reply. Is there any document that mentions about report
> > render limit for each report format (csv, pdf,...)? Thanks.
> >
> >
> > Charles
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> I have done about 60,000 rows but they were small (very few columns).
> >> 200,000 is just past what RS is designed for. My suggestion is to look at
> >> other technologies to do this (like DTS etc).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> >> news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
> >> > Hi Bruce,
> >> >
> >> > I have a similar issue but much more data on a server with 3G memory. I
> >> > use
> >> > RS to render 200,000 rows to CSV and thought that would be better than
> >> > PDF,
> >> > but it took more than 30 minutes and then threw OutOfMemory exeception
> >> > and
> >> > RS
> >> > got restarted many times according to Event log. We already raise
> >> > MaxMemory
> >> > to 120 in the config file, but just don't know why RS still can not
> >> > render
> >> > a
> >> > csv file. We really need to render that much data into a report for
> >> > clients.
> >> > Does anyone know how to use RS deal with that much amount of data? Is
> >> > there
> >> > some other way I can try? Thank you.
> >> >
> >> > Charles
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> 100 rows should not be a problem. Plus you say that if the report
> >> >> comes
> >> >> back
> >> >> in 3 minutes you are OK. This makes me think that it is an IIS issue.
> >> >> That
> >> >> IIS is timing out on you. I have heard of people adjusting something
> >> >> in
> >> >> IIS
> >> >> for this but I am not sure where it is done.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Michael" <mjhaddad@.gmail.com> wrote in message
> >> >> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
> >> >> > Bruce, credentials are fine and the report returns in a little over
> >> >> > 10
> >> >> > minutes from the development environment.
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||It takes the same amount of time. The difference is that Excel recognizes it
as CSV so it does not put it all in one column. This is what I use in jump
to URL. Perhaps it will help you with your subscriptions:
This causes Excel to come up with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:43871106-CE27-47D9-8E6D-66B35B83CF8F@.microsoft.com...
> Hi Bruce,
> Currently I use data driven subscription to render CSV file. How do I
> render
> CSV in ASCII from the subscription? Would it be faster and less memory
> intensive? Thanks.
> Charles
> "Bruce L-C [MVP]" wrote:
>> No, there is not a document. I'm sure it varies depending on the RAM you
>> have and other configuration issues. In general though I would say the
>> product is designed around human consumption not data loads. Sometimes a
>> relatively large amount of data is for use by a person for instance into
>> Excel. Until recently Excel had a limit of 64,000 which when doing CSV RS
>> can handle (at least on my box which has 2 gigs of RAM). One thing you
>> might
>> want to try is to see if the user needs all the columns of the report
>> when
>> you export to CSV. If not, then you could have an alternate report just
>> for
>> that. What I do sometimes is have a report for viewing and a report to
>> exporting. I hide the exporting one in list view and then I add a link
>> with
>> a jump to URL at the top of the report. It exports in CSV ASCII (very
>> important, default by RS is Unicode which Excel does not recognize).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
>> news:C9BBC97A-7E32-4241-ABF5-177FFA654E04@.microsoft.com...
>> > Hi Bruce,
>> >
>> > Thanks for your reply. Is there any document that mentions about report
>> > render limit for each report format (csv, pdf,...)? Thanks.
>> >
>> >
>> > Charles
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> I have done about 60,000 rows but they were small (very few columns).
>> >> 200,000 is just past what RS is designed for. My suggestion is to look
>> >> at
>> >> other technologies to do this (like DTS etc).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
>> >> news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
>> >> > Hi Bruce,
>> >> >
>> >> > I have a similar issue but much more data on a server with 3G
>> >> > memory. I
>> >> > use
>> >> > RS to render 200,000 rows to CSV and thought that would be better
>> >> > than
>> >> > PDF,
>> >> > but it took more than 30 minutes and then threw OutOfMemory
>> >> > exeception
>> >> > and
>> >> > RS
>> >> > got restarted many times according to Event log. We already raise
>> >> > MaxMemory
>> >> > to 120 in the config file, but just don't know why RS still can not
>> >> > render
>> >> > a
>> >> > csv file. We really need to render that much data into a report for
>> >> > clients.
>> >> > Does anyone know how to use RS deal with that much amount of data?
>> >> > Is
>> >> > there
>> >> > some other way I can try? Thank you.
>> >> >
>> >> > Charles
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> 100 rows should not be a problem. Plus you say that if the report
>> >> >> comes
>> >> >> back
>> >> >> in 3 minutes you are OK. This makes me think that it is an IIS
>> >> >> issue.
>> >> >> That
>> >> >> IIS is timing out on you. I have heard of people adjusting
>> >> >> something
>> >> >> in
>> >> >> IIS
>> >> >> for this but I am not sure where it is done.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Michael" <mjhaddad@.gmail.com> wrote in message
>> >> >> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
>> >> >> > Bruce, credentials are fine and the report returns in a little
>> >> >> > over
>> >> >> > 10
>> >> >> > minutes from the development environment.
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Hi Bruce,
Thank you for your hints. But still wondering why RS uses so much memory for
rendering a big report. Have you heard this would be improved in Sql Server
RS 2005?
Charles
"Bruce L-C [MVP]" wrote:
> It takes the same amount of time. The difference is that Excel recognizes it
> as CSV so it does not put it all in one column. This is what I use in jump
> to URL. Perhaps it will help you with your subscriptions:
> This causes Excel to come up with the data in a separate window:
>
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> news:43871106-CE27-47D9-8E6D-66B35B83CF8F@.microsoft.com...
> > Hi Bruce,
> >
> > Currently I use data driven subscription to render CSV file. How do I
> > render
> > CSV in ASCII from the subscription? Would it be faster and less memory
> > intensive? Thanks.
> >
> > Charles
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> No, there is not a document. I'm sure it varies depending on the RAM you
> >> have and other configuration issues. In general though I would say the
> >> product is designed around human consumption not data loads. Sometimes a
> >> relatively large amount of data is for use by a person for instance into
> >> Excel. Until recently Excel had a limit of 64,000 which when doing CSV RS
> >> can handle (at least on my box which has 2 gigs of RAM). One thing you
> >> might
> >> want to try is to see if the user needs all the columns of the report
> >> when
> >> you export to CSV. If not, then you could have an alternate report just
> >> for
> >> that. What I do sometimes is have a report for viewing and a report to
> >> exporting. I hide the exporting one in list view and then I add a link
> >> with
> >> a jump to URL at the top of the report. It exports in CSV ASCII (very
> >> important, default by RS is Unicode which Excel does not recognize).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> >> news:C9BBC97A-7E32-4241-ABF5-177FFA654E04@.microsoft.com...
> >> > Hi Bruce,
> >> >
> >> > Thanks for your reply. Is there any document that mentions about report
> >> > render limit for each report format (csv, pdf,...)? Thanks.
> >> >
> >> >
> >> > Charles
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> I have done about 60,000 rows but they were small (very few columns).
> >> >> 200,000 is just past what RS is designed for. My suggestion is to look
> >> >> at
> >> >> other technologies to do this (like DTS etc).
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Chuck" <Chuck@.discussions.microsoft.com> wrote in message
> >> >> news:A08B17BA-1720-4324-A1ED-96B659CDBAE7@.microsoft.com...
> >> >> > Hi Bruce,
> >> >> >
> >> >> > I have a similar issue but much more data on a server with 3G
> >> >> > memory. I
> >> >> > use
> >> >> > RS to render 200,000 rows to CSV and thought that would be better
> >> >> > than
> >> >> > PDF,
> >> >> > but it took more than 30 minutes and then threw OutOfMemory
> >> >> > exeception
> >> >> > and
> >> >> > RS
> >> >> > got restarted many times according to Event log. We already raise
> >> >> > MaxMemory
> >> >> > to 120 in the config file, but just don't know why RS still can not
> >> >> > render
> >> >> > a
> >> >> > csv file. We really need to render that much data into a report for
> >> >> > clients.
> >> >> > Does anyone know how to use RS deal with that much amount of data?
> >> >> > Is
> >> >> > there
> >> >> > some other way I can try? Thank you.
> >> >> >
> >> >> > Charles
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> 100 rows should not be a problem. Plus you say that if the report
> >> >> >> comes
> >> >> >> back
> >> >> >> in 3 minutes you are OK. This makes me think that it is an IIS
> >> >> >> issue.
> >> >> >> That
> >> >> >> IIS is timing out on you. I have heard of people adjusting
> >> >> >> something
> >> >> >> in
> >> >> >> IIS
> >> >> >> for this but I am not sure where it is done.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Michael" <mjhaddad@.gmail.com> wrote in message
> >> >> >> news:1119475785.897599.226260@.o13g2000cwo.googlegroups.com...
> >> >> >> > Bruce, credentials are fine and the report returns in a little
> >> >> >> > over
> >> >> >> > 10
> >> >> >> > minutes from the development environment.
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||What about matrix report?
I have about 150.000 records which make my matrix report 150 rows and
90 columns.
It does not render to excel:( because of low resources.
please help|||Is this the number of rows returned or the size of the table. It doesn't
matter how big the table is (I go against tables with 50 million rows), what
matters is the number of rows returned. If you have that many rows returned
then you need to look at your query and have the database do more of the
work. The best strategy (not just for RS but for any application) is to
return the smallest number of rows possible. Have SQL Server DB do the work,
not RS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"kamel" <kwiciak@.gmail.com> wrote in message
news:1119644816.435274.296140@.g43g2000cwa.googlegroups.com...
> What about matrix report?
> I have about 150.000 records which make my matrix report 150 rows and
> 90 columns.
> It does not render to excel:( because of low resources.
> please help
>|||My query returns at the moment about 150.000 - 200.000 records.
I use this data on my matrix report.
I have 3 levels of grouping on rows and 3 levels of grouping on columns
and in cells I have also some calculations.
Finally I came up with matrix with about 150 rows and 90 columns.
I does not want to render to excel.