Maximum memory for ASP.NET worker process

We have an application that runs out of memory on our client environment runs
when executing a rather large crystal reports ( about 400000 records) spread
over several 1000 pages. The current production server has about 4GB RAM. Is
there any benefit in increasing this to 6GB so that we can increase the
memory used by ASP.NET or is there a 2GB limit on the memory that a Win32
process can use.
Thanks in advance.if its a dedicated iis box, you can try running with the /3gb switch,
which would allow the asp.net to use up to 3gb.

you should also check what your current max memory is set to.

-- bruce (sqlwork.com)

Frank1213 wrote:

Quote:

Originally Posted by

We have an application that runs out of memory on our client environment runs
when executing a rather large crystal reports ( about 400000 records) spread
over several 1000 pages. The current production server has about 4GB RAM. Is
there any benefit in increasing this to 6GB so that we can increase the
memory used by ASP.NET or is there a 2GB limit on the memory that a Win32
process can use.
Thanks in advance.