Saving DataTable to session vs saving a Custom object.

J

John Kandell

Hi,

Would someone be able to shed some light on what is the cost of saving a
DataTable to session vs saving a custom object of the same data.

For example, let's say I had a DataTable with 1000 records and each record
had 10 columns, how much extra cost is involved in saving that vs, a custom
object with 10 get/set properties in a ArrayList holding 1000 instances of
the object with the same data?


Looking forward to your response.

John
 
M

Matt Berther

Hello John,

Does it have to be saved in Session? Is the data unique per user? Or would
HttpContext.Application or HttpContext.Cache be a better spot for it?

Large objects in session dont scale very well...
 
J

John Kandell

Hi

The data is unique per user.
And we are using SQL server as storage.

Also, the requirement is to keep the HTML as small as possible, so, we can't
use ViewState either.

John
 
J

John Kandell

Just to be clear..., I meant we are using SQL server as storage for session
variables.

Rahul
 
E

eeebop

I don't have an answer for you, but if you've found something, I'd be
curious to know.

Thanks!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,480
Members
44,900
Latest member
Nell636132

Latest Threads

Top