When using the Export feature on a Sql Reporting Services report and
exporting a small (<10MB) report to excel, csv, or pdf takes from 10 to 60
minutes or more. It doesn't matter if you choose Save or Open, a 5 MB
report is taking up to an hour for users to open. We have fast, new
workstations with 1GB of memory but it doesn't seem to matter. When
choosing Save, the download progress UI starts fast at > 1mbs and slows down
to a crawl at .01kbs. The report itself only take 5 seconds to run and
exports fine when exported from the server with Remote Desktop. Is there a
configuration somewhere I'm missing? Any ideas appreciated.
Thanks,
JimThe export is occuring at the server (rendering) so export speeds should
have almost nothing to do with the workstation. You should be seeing pretty
close to the performance you are seeing via remote desktop. The only
difference is the time to move the data (in your case 5 to 10 MB) over the
network. What happens if you export using remote desktop and then from one
of your other PCs try copying it (map a network drive) to a share on the
server where you saved the file.
CSV and html are very very fast. Order of magnitude faster than pdf and
excel.
I think you are having a network problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jims" <biz@.neocasa.net> wrote in message
news:%235DMDPS0GHA.3568@.TK2MSFTNGP03.phx.gbl...
> When using the Export feature on a Sql Reporting Services report and
> exporting a small (<10MB) report to excel, csv, or pdf takes from 10 to 60
> minutes or more. It doesn't matter if you choose Save or Open, a 5 MB
> report is taking up to an hour for users to open. We have fast, new
> workstations with 1GB of memory but it doesn't seem to matter. When
> choosing Save, the download progress UI starts fast at > 1mbs and slows
> down to a crawl at .01kbs. The report itself only take 5 seconds to run
> and exports fine when exported from the server with Remote Desktop. Is
> there a configuration somewhere I'm missing? Any ideas appreciated.
> Thanks,
> Jim
>|||I am extremely shocked that the Export even works.
My experience is that reporting services dies on exports to excel and
PDF (especially pdf).
If you try to export anything with more than hundreds of rows, you
will kill the server memory and cpu.
We've been working with ms for months (SRX060712604389 ). Did tons of
traces, memory dumps, perf monitor.
Their last word was your report is to big see: KB article 909678
Our report had a thousand rows, new quad cpu server, 4gig ram, sql05,
win2003; It puked.
Don't try more than 2 or 3 exports in a row, the server does not like
to release memory, we saw that for each export it would keep a few
hundred megs of memory. Do some exports and watch the memory in task
manager.
On Tue, 5 Sep 2006 15:44:53 -0400, "Jims" <biz@.neocasa.net> wrote:
>When using the Export feature on a Sql Reporting Services report and
>exporting a small (<10MB) report to excel, csv, or pdf takes from 10 to 60
>minutes or more. It doesn't matter if you choose Save or Open, a 5 MB
>report is taking up to an hour for users to open. We have fast, new
>workstations with 1GB of memory but it doesn't seem to matter. When
>choosing Save, the download progress UI starts fast at > 1mbs and slows down
>to a crawl at .01kbs. The report itself only take 5 seconds to run and
>exports fine when exported from the server with Remote Desktop. Is there a
>configuration somewhere I'm missing? Any ideas appreciated.
>Thanks,
>Jim
>|||Note he also says CSV. CSV is very fast and can handle 60,000 rows or more
with no problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chuck P" <Chuck@.newsgroup.nospam> wrote in message
news:45mrg2lehg577debcqo5fcu51l6ih533qn@.4ax.com...
>I am extremely shocked that the Export even works.
> My experience is that reporting services dies on exports to excel and
> PDF (especially pdf).
> If you try to export anything with more than hundreds of rows, you
> will kill the server memory and cpu.
> We've been working with ms for months (SRX060712604389 ). Did tons of
> traces, memory dumps, perf monitor.
> Their last word was your report is to big see: KB article 909678
> Our report had a thousand rows, new quad cpu server, 4gig ram, sql05,
> win2003; It puked.
> Don't try more than 2 or 3 exports in a row, the server does not like
> to release memory, we saw that for each export it would keep a few
> hundred megs of memory. Do some exports and watch the memory in task
> manager.
> On Tue, 5 Sep 2006 15:44:53 -0400, "Jims" <biz@.neocasa.net> wrote:
>>When using the Export feature on a Sql Reporting Services report and
>>exporting a small (<10MB) report to excel, csv, or pdf takes from 10 to 60
>>minutes or more. It doesn't matter if you choose Save or Open, a 5 MB
>>report is taking up to an hour for users to open. We have fast, new
>>workstations with 1GB of memory but it doesn't seem to matter. When
>>choosing Save, the download progress UI starts fast at > 1mbs and slows
>>down
>>to a crawl at .01kbs. The report itself only take 5 seconds to run and
>>exports fine when exported from the server with Remote Desktop. Is there
>>a
>>configuration somewhere I'm missing? Any ideas appreciated.
>>Thanks,
>>Jim|||Setup performance monitor and watch your process
perfmon: private bytes, virtual bytes
You can document the problem, but not fix it.
The problem exists for CSV and PDF, it's more visible in PDF.
On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
<bruce_lcNOSPAM@.hotmail.com> wrote:
>Note he also says CSV. CSV is very fast and can handle 60,000 rows or more
>with no problem.|||The problem exists for Excel and PDF. I have done 60,000 rows with CSV with
no problem. I am not aware of any issues with CSV.
You state CSV is an issue but again, I have not seen it and I have never
seen anyone report it (Excel and PDF, yes).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chuck P" <Chuck@.newsgroup.nospam> wrote in message
news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> Setup performance monitor and watch your process
> perfmon: private bytes, virtual bytes
> You can document the problem, but not fix it.
> The problem exists for CSV and PDF, it's more visible in PDF.
>
> On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> <bruce_lcNOSPAM@.hotmail.com> wrote:
>>Note he also says CSV. CSV is very fast and can handle 60,000 rows or more
>>with no problem.|||I am having same problem, exporting a pdf and excel Takes way to long,
unexceptable for clients. So is there an solution for this? and it is not an
network issue on my end.
"Bruce L-C [MVP]" wrote:
> The problem exists for Excel and PDF. I have done 60,000 rows with CSV with
> no problem. I am not aware of any issues with CSV.
> You state CSV is an issue but again, I have not seen it and I have never
> seen anyone report it (Excel and PDF, yes).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> > Setup performance monitor and watch your process
> > perfmon: private bytes, virtual bytes
> > You can document the problem, but not fix it.
> >
> > The problem exists for CSV and PDF, it's more visible in PDF.
> >
> >
> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >
> >>Note he also says CSV. CSV is very fast and can handle 60,000 rows or more
> >>with no problem.
>
>|||What version? RS 2005 has gotten faster for PDF and Excel. For Excel export
to CSV in ASCII format (rather than Unicode). It will bring it up in Excel
when you do this. CSV is very fast.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Collin Brown - eSolutionsGroup" <Collin Brown -
eSolutionsGroup@.discussions.microsoft.com> wrote in message
news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
>I am having same problem, exporting a pdf and excel Takes way to long,
> unexceptable for clients. So is there an solution for this? and it is not
> an
> network issue on my end.
> "Bruce L-C [MVP]" wrote:
>> The problem exists for Excel and PDF. I have done 60,000 rows with CSV
>> with
>> no problem. I am not aware of any issues with CSV.
>> You state CSV is an issue but again, I have not seen it and I have never
>> seen anyone report it (Excel and PDF, yes).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
>> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
>> > Setup performance monitor and watch your process
>> > perfmon: private bytes, virtual bytes
>> > You can document the problem, but not fix it.
>> >
>> > The problem exists for CSV and PDF, it's more visible in PDF.
>> >
>> >
>> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
>> > <bruce_lcNOSPAM@.hotmail.com> wrote:
>> >
>> >>Note he also says CSV. CSV is very fast and can handle 60,000 rows or
>> >>more
>> >>with no problem.
>>|||I see the same issue. I tuned the query to produce 56,000 rows in < 20 seconds.
The report renders in less then 40 seconds as well.
I put Task Manager server on and see virtual memeory creep up over 1.4 GB
before it hits the cap I had set. When it hits the cap on virtual memeory,
the CPU spins at 100%. This report contains about 10 MB of data so it should
not need 1 GB of memory to run.
Please let me know if there is a fix available.
"Bruce L-C [MVP]" wrote:
> What version? RS 2005 has gotten faster for PDF and Excel. For Excel export
> to CSV in ASCII format (rather than Unicode). It will bring it up in Excel
> when you do this. CSV is very fast.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Collin Brown - eSolutionsGroup" <Collin Brown -
> eSolutionsGroup@.discussions.microsoft.com> wrote in message
> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
> >I am having same problem, exporting a pdf and excel Takes way to long,
> > unexceptable for clients. So is there an solution for this? and it is not
> > an
> > network issue on my end.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> The problem exists for Excel and PDF. I have done 60,000 rows with CSV
> >> with
> >> no problem. I am not aware of any issues with CSV.
> >>
> >> You state CSV is an issue but again, I have not seen it and I have never
> >> seen anyone report it (Excel and PDF, yes).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> >> > Setup performance monitor and watch your process
> >> > perfmon: private bytes, virtual bytes
> >> > You can document the problem, but not fix it.
> >> >
> >> > The problem exists for CSV and PDF, it's more visible in PDF.
> >> >
> >> >
> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >> >
> >> >>Note he also says CSV. CSV is very fast and can handle 60,000 rows or
> >> >>more
> >> >>with no problem.
> >>
> >>
> >>
>
>|||What format are you rendering to?
My only suggestion is compare to CSV.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"serve" <serve@.discussions.microsoft.com> wrote in message
news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
>I see the same issue. I tuned the query to produce 56,000 rows in < 20
>seconds.
> The report renders in less then 40 seconds as well.
> I put Task Manager server on and see virtual memeory creep up over 1.4 GB
> before it hits the cap I had set. When it hits the cap on virtual memeory,
> the CPU spins at 100%. This report contains about 10 MB of data so it
> should
> not need 1 GB of memory to run.
> Please let me know if there is a fix available.
>
> "Bruce L-C [MVP]" wrote:
>> What version? RS 2005 has gotten faster for PDF and Excel. For Excel
>> export
>> to CSV in ASCII format (rather than Unicode). It will bring it up in
>> Excel
>> when you do this. CSV is very fast.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Collin Brown - eSolutionsGroup" <Collin Brown -
>> eSolutionsGroup@.discussions.microsoft.com> wrote in message
>> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
>> >I am having same problem, exporting a pdf and excel Takes way to long,
>> > unexceptable for clients. So is there an solution for this? and it is
>> > not
>> > an
>> > network issue on my end.
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> The problem exists for Excel and PDF. I have done 60,000 rows with CSV
>> >> with
>> >> no problem. I am not aware of any issues with CSV.
>> >>
>> >> You state CSV is an issue but again, I have not seen it and I have
>> >> never
>> >> seen anyone report it (Excel and PDF, yes).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
>> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
>> >> > Setup performance monitor and watch your process
>> >> > perfmon: private bytes, virtual bytes
>> >> > You can document the problem, but not fix it.
>> >> >
>> >> > The problem exists for CSV and PDF, it's more visible in PDF.
>> >> >
>> >> >
>> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
>> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
>> >> >
>> >> >>Note he also says CSV. CSV is very fast and can handle 60,000 rows
>> >> >>or
>> >> >>more
>> >> >>with no problem.
>> >>
>> >>
>> >>
>>|||Bruce thanks for your prompt response.
CSV works just fine, it uses about 180 MB of Memory for the export
Once again, my real question is why does exporting a 20 MB file to excel
chew up more then 1.4 GB of virtual memory?
Based on the previous responses to this thread, I am sure you can reproduce
this issue yourself. This must be a known issue in the Support DB is it not?
My primary concern is not that I can't get my data out of Reporting Server,
but that I have a production report out there with an export option that
will sink our reporting server and mess up the reporting experience for our
other users.
Is there a way to either fix this issue or turn off the excel and pdf export
options for specific reports?
For now all I can do is instruct them to not to use that option on large
data sets.
Sorry to be blunt, but this does not present a professional or bullet proof
solution to my clients deserve.
"Bruce L-C [MVP]" wrote:
> What format are you rendering to?
> My only suggestion is compare to CSV.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "serve" <serve@.discussions.microsoft.com> wrote in message
> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
> >I see the same issue. I tuned the query to produce 56,000 rows in < 20
> >seconds.
> > The report renders in less then 40 seconds as well.
> > I put Task Manager server on and see virtual memeory creep up over 1.4 GB
> > before it hits the cap I had set. When it hits the cap on virtual memeory,
> > the CPU spins at 100%. This report contains about 10 MB of data so it
> > should
> > not need 1 GB of memory to run.
> >
> > Please let me know if there is a fix available.
> >
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> What version? RS 2005 has gotten faster for PDF and Excel. For Excel
> >> export
> >> to CSV in ASCII format (rather than Unicode). It will bring it up in
> >> Excel
> >> when you do this. CSV is very fast.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
> >> >I am having same problem, exporting a pdf and excel Takes way to long,
> >> > unexceptable for clients. So is there an solution for this? and it is
> >> > not
> >> > an
> >> > network issue on my end.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> The problem exists for Excel and PDF. I have done 60,000 rows with CSV
> >> >> with
> >> >> no problem. I am not aware of any issues with CSV.
> >> >>
> >> >> You state CSV is an issue but again, I have not seen it and I have
> >> >> never
> >> >> seen anyone report it (Excel and PDF, yes).
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> >> >> > Setup performance monitor and watch your process
> >> >> > perfmon: private bytes, virtual bytes
> >> >> > You can document the problem, but not fix it.
> >> >> >
> >> >> > The problem exists for CSV and PDF, it's more visible in PDF.
> >> >> >
> >> >> >
> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >> >> >
> >> >> >>Note he also says CSV. CSV is very fast and can handle 60,000 rows
> >> >> >>or
> >> >> >>more
> >> >> >>with no problem.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Looking through the thread I don't see what version you are on. I know that
RS 2005 has gotten better with both Excel and PDF.
There is no way to turn off Excel or PDF for just a particular report.
However, you can configure in one of the configuration files for CSV to use
ASCII format so Excel handles it better (puts all the fields in their own
columns).
All rendering is done in RAM. The working space necessary will depend on the
complexity of the report. You could try a test where you simplify the report
as much as possible and see if that helps. One thing I have done in the past
is have a report just for export. I provided a link at the top of the report
and used Jump to URL to render the report. I would removed grouping,
subtotals, etc etc. Then in report manager I would hide in list view so the
user didn't see the report. Another option for you to try.
As far as the support DB. I do not work for MS and I do not have access to
internal MS tools (like a support DB). Also, I do this on a volunteer basis.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"serve" <serve@.discussions.microsoft.com> wrote in message
news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
> Bruce thanks for your prompt response.
> CSV works just fine, it uses about 180 MB of Memory for the export
> Once again, my real question is why does exporting a 20 MB file to excel
> chew up more then 1.4 GB of virtual memory?
> Based on the previous responses to this thread, I am sure you can
> reproduce
> this issue yourself. This must be a known issue in the Support DB is it
> not?
> My primary concern is not that I can't get my data out of Reporting
> Server,
> but that I have a production report out there with an export option that
> will sink our reporting server and mess up the reporting experience for
> our
> other users.
> Is there a way to either fix this issue or turn off the excel and pdf
> export
> options for specific reports?
> For now all I can do is instruct them to not to use that option on large
> data sets.
> Sorry to be blunt, but this does not present a professional or bullet
> proof
> solution to my clients deserve.
>
> "Bruce L-C [MVP]" wrote:
>> What format are you rendering to?
>> My only suggestion is compare to CSV.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "serve" <serve@.discussions.microsoft.com> wrote in message
>> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
>> >I see the same issue. I tuned the query to produce 56,000 rows in < 20
>> >seconds.
>> > The report renders in less then 40 seconds as well.
>> > I put Task Manager server on and see virtual memeory creep up over 1.4
>> > GB
>> > before it hits the cap I had set. When it hits the cap on virtual
>> > memeory,
>> > the CPU spins at 100%. This report contains about 10 MB of data so it
>> > should
>> > not need 1 GB of memory to run.
>> >
>> > Please let me know if there is a fix available.
>> >
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> What version? RS 2005 has gotten faster for PDF and Excel. For Excel
>> >> export
>> >> to CSV in ASCII format (rather than Unicode). It will bring it up in
>> >> Excel
>> >> when you do this. CSV is very fast.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
>> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
>> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
>> >> >I am having same problem, exporting a pdf and excel Takes way to
>> >> >long,
>> >> > unexceptable for clients. So is there an solution for this? and it
>> >> > is
>> >> > not
>> >> > an
>> >> > network issue on my end.
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> The problem exists for Excel and PDF. I have done 60,000 rows with
>> >> >> CSV
>> >> >> with
>> >> >> no problem. I am not aware of any issues with CSV.
>> >> >>
>> >> >> You state CSV is an issue but again, I have not seen it and I have
>> >> >> never
>> >> >> seen anyone report it (Excel and PDF, yes).
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
>> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
>> >> >> > Setup performance monitor and watch your process
>> >> >> > perfmon: private bytes, virtual bytes
>> >> >> > You can document the problem, but not fix it.
>> >> >> >
>> >> >> > The problem exists for CSV and PDF, it's more visible in PDF.
>> >> >> >
>> >> >> >
>> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
>> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
>> >> >> >
>> >> >> >>Note he also says CSV. CSV is very fast and can handle 60,000
>> >> >> >>rows
>> >> >> >>or
>> >> >> >>more
>> >> >> >>with no problem.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Thanks Bruce, thoese are some very good suggesitons.
Sorry I assumed you worked for microsoft.
I really appreaciate the info you provide on these threads.
The version I am running is 8.00.1038.00.
"Bruce L-C [MVP]" wrote:
> Looking through the thread I don't see what version you are on. I know that
> RS 2005 has gotten better with both Excel and PDF.
> There is no way to turn off Excel or PDF for just a particular report.
> However, you can configure in one of the configuration files for CSV to use
> ASCII format so Excel handles it better (puts all the fields in their own
> columns).
> All rendering is done in RAM. The working space necessary will depend on the
> complexity of the report. You could try a test where you simplify the report
> as much as possible and see if that helps. One thing I have done in the past
> is have a report just for export. I provided a link at the top of the report
> and used Jump to URL to render the report. I would removed grouping,
> subtotals, etc etc. Then in report manager I would hide in list view so the
> user didn't see the report. Another option for you to try.
> As far as the support DB. I do not work for MS and I do not have access to
> internal MS tools (like a support DB). Also, I do this on a volunteer basis.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "serve" <serve@.discussions.microsoft.com> wrote in message
> news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
> > Bruce thanks for your prompt response.
> >
> > CSV works just fine, it uses about 180 MB of Memory for the export
> >
> > Once again, my real question is why does exporting a 20 MB file to excel
> > chew up more then 1.4 GB of virtual memory?
> >
> > Based on the previous responses to this thread, I am sure you can
> > reproduce
> > this issue yourself. This must be a known issue in the Support DB is it
> > not?
> >
> > My primary concern is not that I can't get my data out of Reporting
> > Server,
> > but that I have a production report out there with an export option that
> > will sink our reporting server and mess up the reporting experience for
> > our
> > other users.
> >
> > Is there a way to either fix this issue or turn off the excel and pdf
> > export
> > options for specific reports?
> >
> > For now all I can do is instruct them to not to use that option on large
> > data sets.
> >
> > Sorry to be blunt, but this does not present a professional or bullet
> > proof
> > solution to my clients deserve.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> What format are you rendering to?
> >>
> >> My only suggestion is compare to CSV.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
> >> >I see the same issue. I tuned the query to produce 56,000 rows in < 20
> >> >seconds.
> >> > The report renders in less then 40 seconds as well.
> >> > I put Task Manager server on and see virtual memeory creep up over 1.4
> >> > GB
> >> > before it hits the cap I had set. When it hits the cap on virtual
> >> > memeory,
> >> > the CPU spins at 100%. This report contains about 10 MB of data so it
> >> > should
> >> > not need 1 GB of memory to run.
> >> >
> >> > Please let me know if there is a fix available.
> >> >
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> What version? RS 2005 has gotten faster for PDF and Excel. For Excel
> >> >> export
> >> >> to CSV in ASCII format (rather than Unicode). It will bring it up in
> >> >> Excel
> >> >> when you do this. CSV is very fast.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
> >> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
> >> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
> >> >> >I am having same problem, exporting a pdf and excel Takes way to
> >> >> >long,
> >> >> > unexceptable for clients. So is there an solution for this? and it
> >> >> > is
> >> >> > not
> >> >> > an
> >> >> > network issue on my end.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> The problem exists for Excel and PDF. I have done 60,000 rows with
> >> >> >> CSV
> >> >> >> with
> >> >> >> no problem. I am not aware of any issues with CSV.
> >> >> >>
> >> >> >> You state CSV is an issue but again, I have not seen it and I have
> >> >> >> never
> >> >> >> seen anyone report it (Excel and PDF, yes).
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> >> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> >> >> >> > Setup performance monitor and watch your process
> >> >> >> > perfmon: private bytes, virtual bytes
> >> >> >> > You can document the problem, but not fix it.
> >> >> >> >
> >> >> >> > The problem exists for CSV and PDF, it's more visible in PDF.
> >> >> >> >
> >> >> >> >
> >> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> >> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >> >> >> >
> >> >> >> >>Note he also says CSV. CSV is very fast and can handle 60,000
> >> >> >> >>rows
> >> >> >> >>or
> >> >> >> >>more
> >> >> >> >>with no problem.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||No problem. No MVPs work for MS. They all are volunteers.
You are on RS 2000. RS 2005 has had some substantial improvements with PDF
and Excel. They are still slower than CSV and HTML but I found a distinct
improvement. For instance, with RS 2000 I could have an Excel export that
would lock up the server. I have not had that happen since I upgraded.
Indeed, configuring RS to export CSV as ASCII was specifically due to this
work around of having a link. When I did a jump to URL I would export as
CSV, ASCII using a slimmed down report. I no longer use this technique with
RS 2005.
RS 2005 has other substantial improvements: multi-select parmeters, calendar
control for date parameters, end user sorting, etc. I really recommend going
to it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"serve" <serve@.discussions.microsoft.com> wrote in message
news:ADE9812A-3A1A-45CB-A8DC-6AA8E6542500@.microsoft.com...
> Thanks Bruce, thoese are some very good suggesitons.
> Sorry I assumed you worked for microsoft.
> I really appreaciate the info you provide on these threads.
> The version I am running is 8.00.1038.00.
>
> "Bruce L-C [MVP]" wrote:
>> Looking through the thread I don't see what version you are on. I know
>> that
>> RS 2005 has gotten better with both Excel and PDF.
>> There is no way to turn off Excel or PDF for just a particular report.
>> However, you can configure in one of the configuration files for CSV to
>> use
>> ASCII format so Excel handles it better (puts all the fields in their own
>> columns).
>> All rendering is done in RAM. The working space necessary will depend on
>> the
>> complexity of the report. You could try a test where you simplify the
>> report
>> as much as possible and see if that helps. One thing I have done in the
>> past
>> is have a report just for export. I provided a link at the top of the
>> report
>> and used Jump to URL to render the report. I would removed grouping,
>> subtotals, etc etc. Then in report manager I would hide in list view so
>> the
>> user didn't see the report. Another option for you to try.
>> As far as the support DB. I do not work for MS and I do not have access
>> to
>> internal MS tools (like a support DB). Also, I do this on a volunteer
>> basis.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "serve" <serve@.discussions.microsoft.com> wrote in message
>> news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
>> > Bruce thanks for your prompt response.
>> >
>> > CSV works just fine, it uses about 180 MB of Memory for the export
>> >
>> > Once again, my real question is why does exporting a 20 MB file to
>> > excel
>> > chew up more then 1.4 GB of virtual memory?
>> >
>> > Based on the previous responses to this thread, I am sure you can
>> > reproduce
>> > this issue yourself. This must be a known issue in the Support DB is it
>> > not?
>> >
>> > My primary concern is not that I can't get my data out of Reporting
>> > Server,
>> > but that I have a production report out there with an export option
>> > that
>> > will sink our reporting server and mess up the reporting experience for
>> > our
>> > other users.
>> >
>> > Is there a way to either fix this issue or turn off the excel and pdf
>> > export
>> > options for specific reports?
>> >
>> > For now all I can do is instruct them to not to use that option on
>> > large
>> > data sets.
>> >
>> > Sorry to be blunt, but this does not present a professional or bullet
>> > proof
>> > solution to my clients deserve.
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> What format are you rendering to?
>> >>
>> >> My only suggestion is compare to CSV.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "serve" <serve@.discussions.microsoft.com> wrote in message
>> >> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
>> >> >I see the same issue. I tuned the query to produce 56,000 rows in <
>> >> >20
>> >> >seconds.
>> >> > The report renders in less then 40 seconds as well.
>> >> > I put Task Manager server on and see virtual memeory creep up over
>> >> > 1.4
>> >> > GB
>> >> > before it hits the cap I had set. When it hits the cap on virtual
>> >> > memeory,
>> >> > the CPU spins at 100%. This report contains about 10 MB of data so
>> >> > it
>> >> > should
>> >> > not need 1 GB of memory to run.
>> >> >
>> >> > Please let me know if there is a fix available.
>> >> >
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> What version? RS 2005 has gotten faster for PDF and Excel. For
>> >> >> Excel
>> >> >> export
>> >> >> to CSV in ASCII format (rather than Unicode). It will bring it up
>> >> >> in
>> >> >> Excel
>> >> >> when you do this. CSV is very fast.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
>> >> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
>> >> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
>> >> >> >I am having same problem, exporting a pdf and excel Takes way to
>> >> >> >long,
>> >> >> > unexceptable for clients. So is there an solution for this? and
>> >> >> > it
>> >> >> > is
>> >> >> > not
>> >> >> > an
>> >> >> > network issue on my end.
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> The problem exists for Excel and PDF. I have done 60,000 rows
>> >> >> >> with
>> >> >> >> CSV
>> >> >> >> with
>> >> >> >> no problem. I am not aware of any issues with CSV.
>> >> >> >>
>> >> >> >> You state CSV is an issue but again, I have not seen it and I
>> >> >> >> have
>> >> >> >> never
>> >> >> >> seen anyone report it (Excel and PDF, yes).
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
>> >> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
>> >> >> >> > Setup performance monitor and watch your process
>> >> >> >> > perfmon: private bytes, virtual bytes
>> >> >> >> > You can document the problem, but not fix it.
>> >> >> >> >
>> >> >> >> > The problem exists for CSV and PDF, it's more visible in PDF.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
>> >> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
>> >> >> >> >
>> >> >> >> >>Note he also says CSV. CSV is very fast and can handle 60,000
>> >> >> >> >>rows
>> >> >> >> >>or
>> >> >> >> >>more
>> >> >> >> >>with no problem.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Hi Bruce,
Where can I find the configuration for RS to export CSV as ASCII?
Thank you,
Roman
"Bruce L-C [MVP]" wrote:
> No problem. No MVPs work for MS. They all are volunteers.
> You are on RS 2000. RS 2005 has had some substantial improvements with PDF
> and Excel. They are still slower than CSV and HTML but I found a distinct
> improvement. For instance, with RS 2000 I could have an Excel export that
> would lock up the server. I have not had that happen since I upgraded.
> Indeed, configuring RS to export CSV as ASCII was specifically due to this
> work around of having a link. When I did a jump to URL I would export as
> CSV, ASCII using a slimmed down report. I no longer use this technique with
> RS 2005.
> RS 2005 has other substantial improvements: multi-select parmeters, calendar
> control for date parameters, end user sorting, etc. I really recommend going
> to it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "serve" <serve@.discussions.microsoft.com> wrote in message
> news:ADE9812A-3A1A-45CB-A8DC-6AA8E6542500@.microsoft.com...
> > Thanks Bruce, thoese are some very good suggesitons.
> > Sorry I assumed you worked for microsoft.
> > I really appreaciate the info you provide on these threads.
> >
> > The version I am running is 8.00.1038.00.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Looking through the thread I don't see what version you are on. I know
> >> that
> >> RS 2005 has gotten better with both Excel and PDF.
> >>
> >> There is no way to turn off Excel or PDF for just a particular report.
> >>
> >> However, you can configure in one of the configuration files for CSV to
> >> use
> >> ASCII format so Excel handles it better (puts all the fields in their own
> >> columns).
> >>
> >> All rendering is done in RAM. The working space necessary will depend on
> >> the
> >> complexity of the report. You could try a test where you simplify the
> >> report
> >> as much as possible and see if that helps. One thing I have done in the
> >> past
> >> is have a report just for export. I provided a link at the top of the
> >> report
> >> and used Jump to URL to render the report. I would removed grouping,
> >> subtotals, etc etc. Then in report manager I would hide in list view so
> >> the
> >> user didn't see the report. Another option for you to try.
> >>
> >> As far as the support DB. I do not work for MS and I do not have access
> >> to
> >> internal MS tools (like a support DB). Also, I do this on a volunteer
> >> basis.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
> >> > Bruce thanks for your prompt response.
> >> >
> >> > CSV works just fine, it uses about 180 MB of Memory for the export
> >> >
> >> > Once again, my real question is why does exporting a 20 MB file to
> >> > excel
> >> > chew up more then 1.4 GB of virtual memory?
> >> >
> >> > Based on the previous responses to this thread, I am sure you can
> >> > reproduce
> >> > this issue yourself. This must be a known issue in the Support DB is it
> >> > not?
> >> >
> >> > My primary concern is not that I can't get my data out of Reporting
> >> > Server,
> >> > but that I have a production report out there with an export option
> >> > that
> >> > will sink our reporting server and mess up the reporting experience for
> >> > our
> >> > other users.
> >> >
> >> > Is there a way to either fix this issue or turn off the excel and pdf
> >> > export
> >> > options for specific reports?
> >> >
> >> > For now all I can do is instruct them to not to use that option on
> >> > large
> >> > data sets.
> >> >
> >> > Sorry to be blunt, but this does not present a professional or bullet
> >> > proof
> >> > solution to my clients deserve.
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> What format are you rendering to?
> >> >>
> >> >> My only suggestion is compare to CSV.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> >> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
> >> >> >I see the same issue. I tuned the query to produce 56,000 rows in <
> >> >> >20
> >> >> >seconds.
> >> >> > The report renders in less then 40 seconds as well.
> >> >> > I put Task Manager server on and see virtual memeory creep up over
> >> >> > 1.4
> >> >> > GB
> >> >> > before it hits the cap I had set. When it hits the cap on virtual
> >> >> > memeory,
> >> >> > the CPU spins at 100%. This report contains about 10 MB of data so
> >> >> > it
> >> >> > should
> >> >> > not need 1 GB of memory to run.
> >> >> >
> >> >> > Please let me know if there is a fix available.
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> What version? RS 2005 has gotten faster for PDF and Excel. For
> >> >> >> Excel
> >> >> >> export
> >> >> >> to CSV in ASCII format (rather than Unicode). It will bring it up
> >> >> >> in
> >> >> >> Excel
> >> >> >> when you do this. CSV is very fast.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
> >> >> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
> >> >> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
> >> >> >> >I am having same problem, exporting a pdf and excel Takes way to
> >> >> >> >long,
> >> >> >> > unexceptable for clients. So is there an solution for this? and
> >> >> >> > it
> >> >> >> > is
> >> >> >> > not
> >> >> >> > an
> >> >> >> > network issue on my end.
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> The problem exists for Excel and PDF. I have done 60,000 rows
> >> >> >> >> with
> >> >> >> >> CSV
> >> >> >> >> with
> >> >> >> >> no problem. I am not aware of any issues with CSV.
> >> >> >> >>
> >> >> >> >> You state CSV is an issue but again, I have not seen it and I
> >> >> >> >> have
> >> >> >> >> never
> >> >> >> >> seen anyone report it (Excel and PDF, yes).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> >> >> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> >> >> >> >> > Setup performance monitor and watch your process
> >> >> >> >> > perfmon: private bytes, virtual bytes
> >> >> >> >> > You can document the problem, but not fix it.
> >> >> >> >> >
> >> >> >> >> > The problem exists for CSV and PDF, it's more visible in PDF.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> >> >> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >> >> >> >> >
> >> >> >> >> >>Note he also says CSV. CSV is very fast and can handle 60,000
> >> >> >> >> >>rows
> >> >> >> >> >>or
> >> >> >> >> >>more
> >> >> >> >> >>with no problem.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||You only need to change in one place, rsreportserver.config. Reboot after
the change. The below shows commenting out the existing entry and putting in
the needed change to have CSV export as ASCII
. <!-- <Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
-->
<Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
</DeviceInfo>
</Configuration>
</Extension>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Roman JR." <rkiss_at_opentext_dot_com> wrote in message
news:E8F6F7EF-0655-4471-8C5D-18418A829BD8@.microsoft.com...
> Hi Bruce,
> Where can I find the configuration for RS to export CSV as ASCII?
> Thank you,
> Roman
> "Bruce L-C [MVP]" wrote:
>> No problem. No MVPs work for MS. They all are volunteers.
>> You are on RS 2000. RS 2005 has had some substantial improvements with
>> PDF
>> and Excel. They are still slower than CSV and HTML but I found a distinct
>> improvement. For instance, with RS 2000 I could have an Excel export that
>> would lock up the server. I have not had that happen since I upgraded.
>> Indeed, configuring RS to export CSV as ASCII was specifically due to
>> this
>> work around of having a link. When I did a jump to URL I would export as
>> CSV, ASCII using a slimmed down report. I no longer use this technique
>> with
>> RS 2005.
>> RS 2005 has other substantial improvements: multi-select parmeters,
>> calendar
>> control for date parameters, end user sorting, etc. I really recommend
>> going
>> to it.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "serve" <serve@.discussions.microsoft.com> wrote in message
>> news:ADE9812A-3A1A-45CB-A8DC-6AA8E6542500@.microsoft.com...
>> > Thanks Bruce, thoese are some very good suggesitons.
>> > Sorry I assumed you worked for microsoft.
>> > I really appreaciate the info you provide on these threads.
>> >
>> > The version I am running is 8.00.1038.00.
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Looking through the thread I don't see what version you are on. I know
>> >> that
>> >> RS 2005 has gotten better with both Excel and PDF.
>> >>
>> >> There is no way to turn off Excel or PDF for just a particular report.
>> >>
>> >> However, you can configure in one of the configuration files for CSV
>> >> to
>> >> use
>> >> ASCII format so Excel handles it better (puts all the fields in their
>> >> own
>> >> columns).
>> >>
>> >> All rendering is done in RAM. The working space necessary will depend
>> >> on
>> >> the
>> >> complexity of the report. You could try a test where you simplify the
>> >> report
>> >> as much as possible and see if that helps. One thing I have done in
>> >> the
>> >> past
>> >> is have a report just for export. I provided a link at the top of the
>> >> report
>> >> and used Jump to URL to render the report. I would removed grouping,
>> >> subtotals, etc etc. Then in report manager I would hide in list view
>> >> so
>> >> the
>> >> user didn't see the report. Another option for you to try.
>> >>
>> >> As far as the support DB. I do not work for MS and I do not have
>> >> access
>> >> to
>> >> internal MS tools (like a support DB). Also, I do this on a volunteer
>> >> basis.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >>
>> >> "serve" <serve@.discussions.microsoft.com> wrote in message
>> >> news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
>> >> > Bruce thanks for your prompt response.
>> >> >
>> >> > CSV works just fine, it uses about 180 MB of Memory for the export
>> >> >
>> >> > Once again, my real question is why does exporting a 20 MB file to
>> >> > excel
>> >> > chew up more then 1.4 GB of virtual memory?
>> >> >
>> >> > Based on the previous responses to this thread, I am sure you can
>> >> > reproduce
>> >> > this issue yourself. This must be a known issue in the Support DB is
>> >> > it
>> >> > not?
>> >> >
>> >> > My primary concern is not that I can't get my data out of Reporting
>> >> > Server,
>> >> > but that I have a production report out there with an export option
>> >> > that
>> >> > will sink our reporting server and mess up the reporting experience
>> >> > for
>> >> > our
>> >> > other users.
>> >> >
>> >> > Is there a way to either fix this issue or turn off the excel and
>> >> > pdf
>> >> > export
>> >> > options for specific reports?
>> >> >
>> >> > For now all I can do is instruct them to not to use that option on
>> >> > large
>> >> > data sets.
>> >> >
>> >> > Sorry to be blunt, but this does not present a professional or
>> >> > bullet
>> >> > proof
>> >> > solution to my clients deserve.
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> What format are you rendering to?
>> >> >>
>> >> >> My only suggestion is compare to CSV.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "serve" <serve@.discussions.microsoft.com> wrote in message
>> >> >> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
>> >> >> >I see the same issue. I tuned the query to produce 56,000 rows in
>> >> >> ><
>> >> >> >20
>> >> >> >seconds.
>> >> >> > The report renders in less then 40 seconds as well.
>> >> >> > I put Task Manager server on and see virtual memeory creep up
>> >> >> > over
>> >> >> > 1.4
>> >> >> > GB
>> >> >> > before it hits the cap I had set. When it hits the cap on virtual
>> >> >> > memeory,
>> >> >> > the CPU spins at 100%. This report contains about 10 MB of data
>> >> >> > so
>> >> >> > it
>> >> >> > should
>> >> >> > not need 1 GB of memory to run.
>> >> >> >
>> >> >> > Please let me know if there is a fix available.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> What version? RS 2005 has gotten faster for PDF and Excel. For
>> >> >> >> Excel
>> >> >> >> export
>> >> >> >> to CSV in ASCII format (rather than Unicode). It will bring it
>> >> >> >> up
>> >> >> >> in
>> >> >> >> Excel
>> >> >> >> when you do this. CSV is very fast.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
>> >> >> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
>> >> >> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
>> >> >> >> >I am having same problem, exporting a pdf and excel Takes way
>> >> >> >> >to
>> >> >> >> >long,
>> >> >> >> > unexceptable for clients. So is there an solution for this?
>> >> >> >> > and
>> >> >> >> > it
>> >> >> >> > is
>> >> >> >> > not
>> >> >> >> > an
>> >> >> >> > network issue on my end.
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> The problem exists for Excel and PDF. I have done 60,000 rows
>> >> >> >> >> with
>> >> >> >> >> CSV
>> >> >> >> >> with
>> >> >> >> >> no problem. I am not aware of any issues with CSV.
>> >> >> >> >>
>> >> >> >> >> You state CSV is an issue but again, I have not seen it and I
>> >> >> >> >> have
>> >> >> >> >> never
>> >> >> >> >> seen anyone report it (Excel and PDF, yes).
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
>> >> >> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
>> >> >> >> >> > Setup performance monitor and watch your process
>> >> >> >> >> > perfmon: private bytes, virtual bytes
>> >> >> >> >> > You can document the problem, but not fix it.
>> >> >> >> >> >
>> >> >> >> >> > The problem exists for CSV and PDF, it's more visible in
>> >> >> >> >> > PDF.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
>> >> >> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
>> >> >> >> >> >
>> >> >> >> >> >>Note he also says CSV. CSV is very fast and can handle
>> >> >> >> >> >>60,000
>> >> >> >> >> >>rows
>> >> >> >> >> >>or
>> >> >> >> >> >>more
>> >> >> >> >> >>with no problem.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Excellent..
Thank you
Roman
"Bruce L-C [MVP]" wrote:
> You only need to change in one place, rsreportserver.config. Reboot after
> the change. The below shows commenting out the existing entry and putting in
> the needed change to have CSV export as ASCII
> .. <!-- <Extension Name="CSV"
> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
> -->
> <Extension Name="CSV"
> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
> <Configuration>
> <DeviceInfo>
> <Encoding>ASCII</Encoding>
> </DeviceInfo>
> </Configuration>
> </Extension>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Roman JR." <rkiss_at_opentext_dot_com> wrote in message
> news:E8F6F7EF-0655-4471-8C5D-18418A829BD8@.microsoft.com...
> > Hi Bruce,
> >
> > Where can I find the configuration for RS to export CSV as ASCII?
> >
> > Thank you,
> >
> > Roman
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> No problem. No MVPs work for MS. They all are volunteers.
> >>
> >> You are on RS 2000. RS 2005 has had some substantial improvements with
> >> PDF
> >> and Excel. They are still slower than CSV and HTML but I found a distinct
> >> improvement. For instance, with RS 2000 I could have an Excel export that
> >> would lock up the server. I have not had that happen since I upgraded.
> >> Indeed, configuring RS to export CSV as ASCII was specifically due to
> >> this
> >> work around of having a link. When I did a jump to URL I would export as
> >> CSV, ASCII using a slimmed down report. I no longer use this technique
> >> with
> >> RS 2005.
> >>
> >> RS 2005 has other substantial improvements: multi-select parmeters,
> >> calendar
> >> control for date parameters, end user sorting, etc. I really recommend
> >> going
> >> to it.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> news:ADE9812A-3A1A-45CB-A8DC-6AA8E6542500@.microsoft.com...
> >> > Thanks Bruce, thoese are some very good suggesitons.
> >> > Sorry I assumed you worked for microsoft.
> >> > I really appreaciate the info you provide on these threads.
> >> >
> >> > The version I am running is 8.00.1038.00.
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Looking through the thread I don't see what version you are on. I know
> >> >> that
> >> >> RS 2005 has gotten better with both Excel and PDF.
> >> >>
> >> >> There is no way to turn off Excel or PDF for just a particular report.
> >> >>
> >> >> However, you can configure in one of the configuration files for CSV
> >> >> to
> >> >> use
> >> >> ASCII format so Excel handles it better (puts all the fields in their
> >> >> own
> >> >> columns).
> >> >>
> >> >> All rendering is done in RAM. The working space necessary will depend
> >> >> on
> >> >> the
> >> >> complexity of the report. You could try a test where you simplify the
> >> >> report
> >> >> as much as possible and see if that helps. One thing I have done in
> >> >> the
> >> >> past
> >> >> is have a report just for export. I provided a link at the top of the
> >> >> report
> >> >> and used Jump to URL to render the report. I would removed grouping,
> >> >> subtotals, etc etc. Then in report manager I would hide in list view
> >> >> so
> >> >> the
> >> >> user didn't see the report. Another option for you to try.
> >> >>
> >> >> As far as the support DB. I do not work for MS and I do not have
> >> >> access
> >> >> to
> >> >> internal MS tools (like a support DB). Also, I do this on a volunteer
> >> >> basis.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >>
> >> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> >> news:9B26C992-D623-459A-BC22-0CC144E0187F@.microsoft.com...
> >> >> > Bruce thanks for your prompt response.
> >> >> >
> >> >> > CSV works just fine, it uses about 180 MB of Memory for the export
> >> >> >
> >> >> > Once again, my real question is why does exporting a 20 MB file to
> >> >> > excel
> >> >> > chew up more then 1.4 GB of virtual memory?
> >> >> >
> >> >> > Based on the previous responses to this thread, I am sure you can
> >> >> > reproduce
> >> >> > this issue yourself. This must be a known issue in the Support DB is
> >> >> > it
> >> >> > not?
> >> >> >
> >> >> > My primary concern is not that I can't get my data out of Reporting
> >> >> > Server,
> >> >> > but that I have a production report out there with an export option
> >> >> > that
> >> >> > will sink our reporting server and mess up the reporting experience
> >> >> > for
> >> >> > our
> >> >> > other users.
> >> >> >
> >> >> > Is there a way to either fix this issue or turn off the excel and
> >> >> > pdf
> >> >> > export
> >> >> > options for specific reports?
> >> >> >
> >> >> > For now all I can do is instruct them to not to use that option on
> >> >> > large
> >> >> > data sets.
> >> >> >
> >> >> > Sorry to be blunt, but this does not present a professional or
> >> >> > bullet
> >> >> > proof
> >> >> > solution to my clients deserve.
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> What format are you rendering to?
> >> >> >>
> >> >> >> My only suggestion is compare to CSV.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "serve" <serve@.discussions.microsoft.com> wrote in message
> >> >> >> news:CD8A0E27-DB6B-4EF5-8F4B-0EDD7884A168@.microsoft.com...
> >> >> >> >I see the same issue. I tuned the query to produce 56,000 rows in
> >> >> >> ><
> >> >> >> >20
> >> >> >> >seconds.
> >> >> >> > The report renders in less then 40 seconds as well.
> >> >> >> > I put Task Manager server on and see virtual memeory creep up
> >> >> >> > over
> >> >> >> > 1.4
> >> >> >> > GB
> >> >> >> > before it hits the cap I had set. When it hits the cap on virtual
> >> >> >> > memeory,
> >> >> >> > the CPU spins at 100%. This report contains about 10 MB of data
> >> >> >> > so
> >> >> >> > it
> >> >> >> > should
> >> >> >> > not need 1 GB of memory to run.
> >> >> >> >
> >> >> >> > Please let me know if there is a fix available.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> What version? RS 2005 has gotten faster for PDF and Excel. For
> >> >> >> >> Excel
> >> >> >> >> export
> >> >> >> >> to CSV in ASCII format (rather than Unicode). It will bring it
> >> >> >> >> up
> >> >> >> >> in
> >> >> >> >> Excel
> >> >> >> >> when you do this. CSV is very fast.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Collin Brown - eSolutionsGroup" <Collin Brown -
> >> >> >> >> eSolutionsGroup@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:993A6C18-93C6-4C1E-9F9B-5198C08DF1B7@.microsoft.com...
> >> >> >> >> >I am having same problem, exporting a pdf and excel Takes way
> >> >> >> >> >to
> >> >> >> >> >long,
> >> >> >> >> > unexceptable for clients. So is there an solution for this?
> >> >> >> >> > and
> >> >> >> >> > it
> >> >> >> >> > is
> >> >> >> >> > not
> >> >> >> >> > an
> >> >> >> >> > network issue on my end.
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> The problem exists for Excel and PDF. I have done 60,000 rows
> >> >> >> >> >> with
> >> >> >> >> >> CSV
> >> >> >> >> >> with
> >> >> >> >> >> no problem. I am not aware of any issues with CSV.
> >> >> >> >> >>
> >> >> >> >> >> You state CSV is an issue but again, I have not seen it and I
> >> >> >> >> >> have
> >> >> >> >> >> never
> >> >> >> >> >> seen anyone report it (Excel and PDF, yes).
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Chuck P" <Chuck@.newsgroup.nospam> wrote in message
> >> >> >> >> >> news:sfc2i2h504b523urvap4eoai84os3us7cg@.4ax.com...
> >> >> >> >> >> > Setup performance monitor and watch your process
> >> >> >> >> >> > perfmon: private bytes, virtual bytes
> >> >> >> >> >> > You can document the problem, but not fix it.
> >> >> >> >> >> >
> >> >> >> >> >> > The problem exists for CSV and PDF, it's more visible in
> >> >> >> >> >> > PDF.
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > On Mon, 18 Sep 2006 09:45:22 -0500, "Bruce L-C [MVP]"
> >> >> >> >> >> > <bruce_lcNOSPAM@.hotmail.com> wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >>Note he also says CSV. CSV is very fast and can handle
> >> >> >> >> >> >>60,000
> >> >> >> >> >> >>rows
> >> >> >> >> >> >>or
> >> >> >> >> >> >>more
> >> >> >> >> >> >>with no problem.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Bruce,
this setting does not work:
<Extension Name=3D"CSV"
Type=3D"Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microso=ft=AD.ReportingServices.CsvRendering">
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
</DeviceInfo>
</Configuration>
</Extension>
after commenting original setting and putting the new one ReportServer
service does not start
any help?|||Ohh...it was my mistake commenting original setting. It works ok.
I have got one more problem: I can not find a way to set csv export as
TAB delimited.
Could somone help with that?
TIA,
Kamel|||Hi,
I am also encountering issues when exporting my reports as Tab Delimited. I
hope someone could help.
Thanks,
Jan
"kamel" wrote:
> Ohh...it was my mistake commenting original setting. It works ok.
> I have got one more problem: I can not find a way to set csv export as
> TAB delimited.
> Could somone help with that?
> TIA,
> Kamel
>
