datareader vs dataset

[rodchar]

hey all,

Regarding paging and sorting in a datagrid, is it better to:

A:
persist a dataset in session

or

B:
use a datareader as a datasource for my datagrid

or

C:
you know a better way than the above

thanks,
rodchar

[Scott Allen]

There are many more details to evaluate, really, like how much data
will be in the DataSet and how many users will you have.

The easiest solution, if you have the server resources, is to cache
the DataSet in the Cache object and use it for paging and sorting.
Paging and sorting with a data reader takes a lot more code and
testing.

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Sat, 5 Nov 2005 18:32:04 -0800, "rodchar"
<ro*****@discussions.microsoft.com> wrote:

hey all,

Regarding paging and sorting in a datagrid, is it better to:

A:
persist a dataset in session

or

B:
use a datareader as a datasource for my datagrid

or

C:
you know a better way than the above

thanks,
rodchar

[rodchar]

would caching the dataset cause problems if you have many users using
application at the same time?

for example, i was caching a dataset and when many users from different
departments started using it in a training class everybody was seeing
information from all departments instead of just theirs.

"Scott Allen" wrote:

There are many more details to evaluate, really, like how much data
will be in the DataSet and how many users will you have.

The easiest solution, if you have the server resources, is to cache
the DataSet in the Cache object and use it for paging and sorting.
Paging and sorting with a data reader takes a lot more code and
testing.

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Sat, 5 Nov 2005 18:32:04 -0800, "rodchar"
<ro*****@discussions.microsoft.com> wrote:

hey all,

Regarding paging and sorting in a datagrid, is it better to:

A:
persist a dataset in session

or

B:
use a datareader as a datasource for my datagrid

or

C:
you know a better way than the above

thanks,
rodchar

[Scott Allen]

On Sat, 5 Nov 2005 22:58:03 -0800, "rodchar"
<ro*****@discussions.microsoft.com> wrote:

would caching the dataset cause problems if you have many users using
application at the same time?

for example, i was caching a dataset and when many users from different
departments started using it in a training class everybody was seeing
information from all departments instead of just theirs.

Not if you cache the objects properly. Keeping the cached DataSet
objects in Session would be one way to make sure they are only
available to a specific user.

The cache can be more useful since it provides more options for
managing the duration of the cached object, but since the cache has an
application wide scope you have to make sure you use a cache key that
scopes a cached piece of data to a specific user (if the data is
specific to a user).

Know what I mean?

--
Scott
http://www.OdeToCode.com/blogs/scott/

[rodchar]

Thank you very much for this insight.

"Scott Allen" wrote:

On Sat, 5 Nov 2005 22:58:03 -0800, "rodchar"
<ro*****@discussions.microsoft.com> wrote:

would caching the dataset cause problems if you have many users using
application at the same time?

for example, i was caching a dataset and when many users from different
departments started using it in a training class everybody was seeing
information from all departments instead of just theirs.

Not if you cache the objects properly. Keeping the cached DataSet
objects in Session would be one way to make sure they are only
available to a specific user.

The cache can be more useful since it provides more options for
managing the duration of the cached object, but since the cache has an
application wide scope you have to make sure you use a cache key that
scopes a cached piece of data to a specific user (if the data is
specific to a user).

Know what I mean?

--
Scott
http://www.OdeToCode.com/blogs/scott/