Export to Excel fails - ASPNET_WP.EXE consumes 60% RAM

I'm trying to export a report to Excel that contains 60,000 rows (but not
more than Excels 65,000 limit) and I get an "internal server error".
When I check the event log on the server it states that aspnet_wp.exe
terminated the report process because it had consumed more than 60% of the
servers availible RAM (1Gb total).
PDF and CSV work fine. Does anyone know anything about this'
--
Cheers
NickExporting to Excel is quite intensive on resources. The problem is that MS
is trying for very high fidelity on what the data looks like. For instance
if you have drill down it creates a spreadsheet with drilldown. For that
amount of data I suggest that you use CSV in ASCII format (the default is
Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
With ASCII format Excel properly puts them in the correct columns. Another
tip, for your table in the report, click on each field of the detail and
make sure it has the name that you want on Export. The CSV export uses this
name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
the deviceinfo (or something like that, doing this from memory from home).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> I'm trying to export a report to Excel that contains 60,000 rows (but not
> more than Excels 65,000 limit) and I get an "internal server error".
> When I check the event log on the server it states that aspnet_wp.exe
> terminated the report process because it had consumed more than 60% of the
> servers availible RAM (1Gb total).
> PDF and CSV work fine. Does anyone know anything about this'
> --
> Cheers
> Nick|||Thanks. I have already managed to get the same report to export to CSV. I'm
trying to prove reporting services out before my company goes down that
track. The performance on exports to Excel is disapointing, i would have
hoped it was better than PDF as it's an MS technology.
--
Cheers
Nick
"Bruce L-C [MVP]" wrote:
> Exporting to Excel is quite intensive on resources. The problem is that MS
> is trying for very high fidelity on what the data looks like. For instance
> if you have drill down it creates a spreadsheet with drilldown. For that
> amount of data I suggest that you use CSV in ASCII format (the default is
> Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
> With ASCII format Excel properly puts them in the correct columns. Another
> tip, for your table in the report, click on each field of the detail and
> make sure it has the name that you want on Export. The CSV export uses this
> name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
> the deviceinfo (or something like that, doing this from memory from home).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
> news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> > I'm trying to export a report to Excel that contains 60,000 rows (but not
> > more than Excels 65,000 limit) and I get an "internal server error".
> >
> > When I check the event log on the server it states that aspnet_wp.exe
> > terminated the report process because it had consumed more than 60% of the
> > servers availible RAM (1Gb total).
> >
> > PDF and CSV work fine. Does anyone know anything about this'
> > --
> > Cheers
> > Nick
>
>|||Yeah...one would think...although I have seen a significant performance
improvement in service pack 2.
Nick Prudhoe wrote:
> Thanks. I have already managed to get the same report to export to CSV. I'm
> trying to prove reporting services out before my company goes down that
> track. The performance on exports to Excel is disapointing, i would have
> hoped it was better than PDF as it's an MS technology.
>