Application-wide DataSet

[Guest]

Hi there!

Many of you already discussed of datasets stored in cache for an asp.net
application.

I stored a "large?" dataset (nearly 4000 records) in an Application
variable, which contains a cached copy of all main tables (four) from a SQL
database, and some calculated statistics. Data in this tables is used in many
webcontrols on nearly all webforms in the application (datagrids,
dropdownlists and treeviews). SQL queries to get this data were not very
fast, so I decided to put everything in cache.

Users may also update data, which forces me to keep the cached dataset
constantly updated.

Now I worked on those sql queries to improve their performance, and got them
fast enough to let me think that maybe I don't need a cached dataset. But the
database could grow, hindering the performance of the queries, or consuming
more memory in the cached dataset.

I really don't know if I should continue to use a cached dataset or simply
read/write directly to/from the database on each web request.

Anybody could give me some suggestion? Thank you!

Bye!

 

[Karl Seguin [MVP]]

Not sure why you need to look at this as an all-or nothing. Can't sub-parts
of your data be cached? the more stale data? Even if it's the smaller piece
of information, it might help reduce the overall load.

Karl