dataset and concurrency

  • Thread starter Thread starter abcd
  • Start date Start date
A

abcd

I am trying to understand datasets. It says its disconnected blah blah.....
Can some one explain me what happens exactly when...

Say I have asp.net page in which Page_load is opening a dataset. So for
every request will a separate dataset be opened...say 100 users are
requesting so will there be 100 different datasets...??? When the dataset is
opened which memory space its uses...is it server memory for that particular
request? Will there be memory issues and hence the performance bottleneck.

How the concurrency works in disconnected architecture here...
 
abcd said:
I am trying to understand datasets. It says its disconnected blah blah.....
Can some one explain me what happens exactly when...

Say I have asp.net page in which Page_load is opening a dataset. So for
every request will a separate dataset be opened...say 100 users are
requesting so will there be 100 different datasets...???

Unless you are sharing one, yes.

When the dataset is
opened which memory space its uses...is it server memory for that
particular request?

Since the code is executed on server, yes, the server memory is used.

Will there be memory issues and hence the performance bottleneck.

Unless you open gigantic datasets there won't be memory issues (depends on
the number of simultaneous opened datasets and server memory of course).
But is shouldn't be a problem as you should load only data necessary and
those data shouldn't be large.
How the concurrency works in disconnected architecture here...

Optimistic concurrency kicks in when you save the dataset to the database
(if you have properly configured dataadapters).
 
Back
Top