Hi Avinash Datasets are the cache on client side and it is useful if you want that your application must't ask the same information again and again from the server. What you can do is to cache it on the client side and read the cache when you need the information again. You can use the data adapters to selectively fill this cache. You don't have to get the millions of records from the Database if you only need 10 records. In memory database gives you the possibility query your cache as a database.
The ADO.net is disconnected from the server and you don't need to block expensive resources while you don't need them. Sandeep -----Original Message----- From: Patrick Steele [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 25. Juni 2002 17:05 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] ADO.NET Datasets [NOTE: This list is closing 7/1/2002. This question should probably go to DOTNET-CLR]. Datasets are disconnected, in-memory representations of data. The advantage is that you *don't* hold a connection (an expensive resource) while doing something with the data. With a dataset, you 1) connect 2) get the data 3) disconnect Your application then loops through the dataset to process the data. This leads to better scalability since you use server resources for a short amount of time. As for your one-million row table -- No, it wouldn't be a good idea to keep that in memory. :) But why would you want to? Can your users really navigate through a million rows and make meaningful updates? I think the better approach is to define how they will process a subset of the data (through paging or filtering of the resultset). --- Patrick Steele ([EMAIL PROTECTED]) Lead Software Architect Image Process Design -----Original Message----- From: Avinash Lakshman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 25, 2002 10:57 AM To: [EMAIL PROTECTED] Subject: [DOTNET] ADO.NET Datasets Hi Here are the questions I have as I am getting my feet wet with ADO.NET : (1) Why Datasets ? What is the need to have an in memory representation of the DB & some of the DB's we deal with have tables that have a million records -- in this case would it be prudent to have an in memory representation of this table ? (2)Also I have seen a lot of literature with respect to disconnected feature of ADO.NET. Could someone please tell me what the disconected feature is all about ? If these are elementary I apologize but I want to know what is the underlying problem this architecture is trying to address. TIA Avinash Join the world's largest e-mail service with MSN Hotmail. Click Here You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
