By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,569 Members | 1,422 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,569 IT Pros & Developers. It's quick & easy.

DataTable vs DataSet ( and Caching )

P: n/a
Hey, all -

I'm working on a project where I'm storing a relatively small amount of
'featured' product information in cache - about 30 records, not updated very
frequently. They get selected from randomly 3 or 4 at a time and are
displayed on pretty much every page of the site, in a DataList (and using
keys). At the moment, I'm storing this information in a DataTable and
putting it in cache. There isn't any sort of relation needed to be set up
between this DataTable or any other I may keep in memory, so I figured I
could do without the DataSet.

So my questions are:

Am I saving any overhead by working with an individual DataTable as opposed
to a DataSet with one DataTable in it?

Does it make it easier for the cache to manage multiple individual
DataTables instead of one DataSet containing those DataTables - in that, it
can drop a DataTable if resources get low, instead of dropping an entire

Am I better off storing this info in another way? An ArrayList? I haven't
messed around much with any of the Collection objects - newb here. I suppose
my preference would be to be able to still reference 'column names' in my
DataBinding expressions in the ItemTemplate, and to set the DataKeys to my
featured products' productID.

Anyway, I'm probably misunderstanding some pretty large basic concepts here,
so feel free to point out the obvious. Thanks in advance!

Nov 18 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.