Check the Microsoft MSDN doco ( search DataReader and DataSet ) :-) Since he mentioned the select , insert etc options he was not using the faster data reader. The benchmark also says XML is the fastest for updates.
Basically the overhead of datasets for small work or updates is quite high. The problem with inserts/ updates is they are done 1 at a time. If update priority is important you need to handcode this likewise if quick small data reads are required you need to handcode some dataReader code. Datasets are good but they are designed for large amounts of data . eg it takes almost the same amount of time to retreive 100 records from a dB as 1 record -datasets are designed to take advantage of this. eg give me all records of this type after which you have an in memory cache. For very large databases datasets , memory is the limit and you need to think about them in terms of a cache structure . eg get so many records put it in a dataset. Check the dataset before going to the DB. You will also need some code to handle syncronised updates. I rarely use the faster datareader and prefer to use large dataset based caches but none of my projects require heavy update performance. Ben -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Franklin Gray Sent: Tuesday, 15 October 2002 9:38 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Learning to work with layers. "The only thing so far is you look like using the standard .NET DB access. These have slow updates." by Ben Got a reference to this? "In addition .NET select method are effecient only if you need to get the data in big chunks preferably whole tables which means you will need lots of memory." by Ben How so? I am asking these questions because it is the first I have heard of it. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
