NEWBIE: How much "disconnected data" it too much?

Dear Experts,

I'm a C# newbie (via Java) looking at ADO.NET for the first time.

I'm trying to understand when you would use "disconnected data", using DataSets and DataAdapters.  My understanding so far is that although the "disconnected data" behaves as though it were a little mini-database, it's all actually being stored IN MEMORY.  Is that right?

If so, it seems there must be some vague upper limit.  For instance, my Java application might currently retrieve 100,000 customer records, each of say 500 bytes (=50Meg), using a traditional "connected" ResultSet.  Is it practical to hold all that in a "disconnected" DataSet?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It is true that datasets hold the data in memory.

Although I don't know the upper-limit, I would definitely say that 100,000 records is a bit too much to hold in memory. It's wise to select only the data that you need. It's better to connect a few times to do your database processing then it is to connect once and get a huge lump of data, I believe. Someone will probably know more about this then I do, but that's my opinion.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
it really depends on how much your machine and application can cope with, aswell as what the data is used for

for a windows app on a machine with a gig of ram, 50meg is nothing really
for a web app on a server with 32 gig of ram, 50meg per session will be fine for a small number of users but once you get a few hundred it'll die

if you're constantly using the data, and it's pretty static, it may be best to keep it in memory instead of repeatedly retrieving it from a database/file.
BrianMc1958Author Commented:
Thanks again!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.