Re: Keeping a DataView in Memory
- From: "Fred Block" <fblock_no_spamming@xxxxxxxxx>
- Date: Wed, 17 Dec 2008 23:27:25 -0500
Hi William,
Thanks again for the response. I'll make a note of that.
Also - I'll be picking up the book you wrote that's on the market now as I'm
sure it'll be a huge help!
Merry Christmas!
Kind regards - Fred
"William Vaughn (MVP)" <billva@xxxxxxxxxxxxxxx> wrote in message
news:e%23fhdmJYJHA.4072@xxxxxxxxxxxxxxxxxxxxxxx
Of course if you've been reading my books you would know that the impact
of a reasonably-constructed DataSet (of <1000 rows) is small. Yes, it
should be kept in memory if you can use it to avoid more round trips.
And no, I'm not working on an ADO.NET 3.5 book 'cause by the time it was
printed MS will have abandoned 3.5 and moved to more fun stuff for another
18 months (or less). I'm not a fan of LINQ or the EF so it's not likely
that I'll be doing another. The 7th edition took about 30 months to write.
I can't afford to donate that kind of time any more.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com/blog/billva
http://betav.com
____________________________________________________________________________________________
"Fred Block" <fblock_no_spamming@xxxxxxxxx> wrote in message
news:uwMMjUIYJHA.2620@xxxxxxxxxxxxxxxxxxxxxxx
Hi and thanks!
Being new to this may I ask if I "should" keep the DataSet in memory or
is that not needed after the table is created? I'm not sure of the
pecking order of these objects.
BTW - I own older books if yours and they're "awesome". Are you working
on one for ADO.NET 3.5?
Thanks again!
Kind regards - Fred
"William Vaughn (MVP)" <billva@xxxxxxxxxxxxxxx> wrote in message
news:%238OXeAIYJHA.5336@xxxxxxxxxxxxxxxxxxxxxxx
A DataView is simply a filtered "view" of a DataTable. As long as the
DataTable is not destroyed, it remains in memory.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com/blog/billva
http://betav.com
____________________________________________________________________________________________
"Fred Block" <fblock_no_spamming@xxxxxxxxx> wrote in message
news:#DwuCRAYJHA.256@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
What is the best way to keep a DataView in memory? I need to access it
often (using "Find" to get data from it repeatedly) and then process
other data based on what I pull from it. I'm thinking a class but I'm
new to ADO.NET and OOP (for the most part). I was also thinking this
may give better performance than repeated calls using a stored
procedure.
I thought at first module level variables...
Also - Will I need to keep the DataSet and/or DataTable open too used
to ?
All thoughts and ideas are greatly appreciated with many thanks in
advance!
Kind regards - Fred
.
- References:
- Keeping a DataView in Memory
- From: Fred Block
- Re: Keeping a DataView in Memory
- From: William Vaughn \(MVP\)
- Re: Keeping a DataView in Memory
- From: Fred Block
- Re: Keeping a DataView in Memory
- From: William Vaughn \(MVP\)
- Keeping a DataView in Memory
- Prev by Date: Re: Keeping a DataView in Memory
- Next by Date: RE: Keeping a DataView in Memory
- Previous by thread: Re: Keeping a DataView in Memory
- Next by thread: Re: Keeping a DataView in Memory
- Index(es):
Relevant Pages
|
