Re: Keeping a DataView in Memory
- From: "William Vaughn \(MVP\)" <billva@xxxxxxxxxxxxxxx>
- Date: Mon, 22 Dec 2008 16:03:21 -0800
ADO and ADO.NET Examples and Best Practices is written for developers transitioning to ADO.NET and has a wealth of fundamental material for those getting started. The 7th Edition takes up where the ADO.NET E&BP book leaves off and talks about the ADO.NET that ships with VS 2005 and far more on SQL Server, the tools and how to design successful applications.
No, I have no idea how authors make money on tech books. They don't stay on the shelves (being pushed off by more recent content) long enough to pay off the advances.
--
__________________________________________________________________________
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:eKBa0dhYJHA.2084@xxxxxxxxxxxxxxxxxxxxxxx
Hi William,.
Thanks a ton for that tip! That did seem to make the data return way faster. It's easy for me to notice because the data is coming from a remote SQL connection. With this application on the actual server, I suppose it'll be light-speed now. I appreciate your time and your input with this topic.
May ask you to recommend one of your two books for me being an ADO.NET beginner please? ADO.NET and ADO Examples and Best Practices for VB Programmers, 2nd Edition -or- Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
I'd like both but I'm budgeted for one now...
Thanks! -- Fred
"William Vaughn (MVP)" <billva@xxxxxxxxxxxxxxx> wrote in message news:uMzTWLYYJHA.4424@xxxxxxxxxxxxxxxxxxxxxxxAnd you don't need a DataAdapter either. Open a DataReader, use the new DataTable.Load method. It's light and fast. Set your DataView properties to filter or sort as needed.
--
__________________________________________________________________________
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
____________________________________________________________________________________________
"Kenny" <Kenny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:FC80A9F5-B1A6-4DD0-BC0A-F36F4A871BF4@xxxxxxxxxxxxxxxxOften ... I don't even use a DataSet.
I define a DataTable().
Fill it with a DataAdapter.
"Index" it with a DataView.
As long as the DataTable and DataView object remain in scope then you can
play with the DataView all you like.
"Fred Block" wrote:
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
- Follow-Ups:
- Re: Keeping a DataView in Memory
- From: Fred Block
- Re: Keeping a DataView in Memory
- References:
- Keeping a DataView in Memory
- From: Fred Block
- RE: Keeping a DataView in Memory
- From: Kenny
- Re: Keeping a DataView in Memory
- From: William Vaughn \(MVP\)
- Re: Keeping a DataView in Memory
- From: Fred Block
- Keeping a DataView in Memory
- Prev by Date: Re: ADO.NET Data Services
- Next by Date: Re: Iteration of Large Result Set
- Previous by thread: Re: Keeping a DataView in Memory
- Next by thread: Re: Keeping a DataView in Memory
- Index(es):
Relevant Pages
|
Loading