If the data does not change often, caching the data once for the application
is a good idea. If the data does change, but not for a session, then caching
for session is a good idea. I employ the technique regularly, as fetching
the same result set over and over is NOT a wise idea, unless it is changing
some how.
Performance issues? Provided you are not storing huge chunks of the database
in memory (or worse in memory for every session), you will find that the
issue is it performs much better than pulling the data every time.
--
Gregory A. Beamer
*************************************************
Think Outside the Box!
*************************************************
"msuk" <ms**@discussions.microsoft.com> wrote in message
news:D1**********************************@microsof t.com...
All,
I have a VB.NET/ASP.NET application that uses some common data throughout.
Now what I would like to do is instead of hitting the database every time
to
fetch back two dataset of 5 rows 2 cols I would like to use the
application
object to store these 2 dataset. I would like to know if this is
advisable
and will there be any performance issues?
Thanks
Msuk