I'm trying to return a DataTable with 146k rows * 41 columns. Returning
smaller sets works but the larger ones throw this exception. I saw there was
a bug in 1.0 sp 1 &2 but I thought it was fixed by now. Are there any
suggestions on what could be the cause?
The remoting object is being hosted by IIS and the machine has 2 gigs of
physical ram. w3wp.exe shows a max usage of 503 megs of ram.
Joe,
Can you save the DataSet to a file using WriteXml and tell us its size?
Sorry, I don't have the answer but can suggest what might be a workaround.
DataSet always serilaizes to XML. If values you return are small the overhead
XML verbosity imposes can be enormous. You could try to do your own serialization.
Alexander
> I'm trying to return a DataTable with 146k rows * 41 columns.
> Returning smaller sets works but the larger ones throw this exception.
[quoted text clipped - 3 lines]
> The remoting object is being hosted by IIS and the machine has 2 gigs
> of physical ram. w3wp.exe shows a max usage of 503 megs of ram.
M.Posseth - 28 Feb 2005 07:39 GMT
Joe
if you are really passing a datatable object , try it with a dataset this
might solve your problem
i noticed already strange behaviors with datable objects and remoting /
webservices
Even better with webservices you can`t pass datatables at all only when they
are contained inside datasets this behavior is by design
( in my opinion this breaks good OOP but that is another story )
http://support.microsoft.com/default.aspx?scid=kb;en-us;306134

Signature
Met vriendelijke groet
Kind regards,
Michel Posseth
Software Developer
Microsoft Certified Professional
> Joe,
>
[quoted text clipped - 13 lines]
> > The remoting object is being hosted by IIS and the machine has 2 gigs
> > of physical ram. w3wp.exe shows a max usage of 503 megs of ram.