Thanks for your reply. When you said that it would probably run fine if IIS
renders large CSV reprots. That's what I saw in Task Manager. Is it right? If
"Wayne Snyder" wrote:
> Reporting Services MUST have the entire data set in memory ( in most cases )
> prior to doing any rendering. If the data can not fit into memory, the
> report can not run... However the limit should be the max memory that a
> process can have on the OS 2GByte by default, but you can use the /3GB and
> AWE, etc switches to increase the memory. 64 bit will be available soon.
>
> If SQL is also running on the 3G server then RS ( Actually IIS w3wp.exe) is
> not getting as much memory as it could... You would benefit from adding
> memory to the box... 200k rows, would probably run fine if IIS could get 2.5
> GB of memory....
>
> Another alternative is to break the report down into smaller sections...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
>
www.mariner-usa.com > (Please respond only to the newsgroups.)
>
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
>
www.sqlpass.org >
> "Chuck" <Chuck@discussions.microsoft.com> wrote in message
> news:51BD555C-4A14-48C6-ADEF-3643DBD9CA96@microsoft.com...
> > Hi,
> >
> > RS has SP2 and 3G memory in a server. 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
> >
>
>
