Ado net updating
The model for how it is used is very similar to a classic ADO recordset configured to use client cursor, except that rather than moving a logical cursor, the Data Table’s Rows collection is indexed to reach a particular row.
The dark side of using Data Sets is that the data remains in memory for as long as you use it.
If you need read-only access to the data, something often done inside an ASP. Unless you are going to persist the data between postbacks, the data that you use to, say, populate a grid, will not be present when someone clicks on one of the rows of that grid. NET application model is that there will be a number of independent requests, and between requests, a client will not maintain a connection to the database. NET provides session state, a way of maintaining the appearance of a stateful application, but storing a client-specific Data Set in session state is not considered good form and may limit the scalability of your application.
NET Web Services accepts parameters of type Data Set and return values of type Data Set.While this can be powerful, it does limit your application to .NET consumers of your web service, since the Data Set is not accepted by web services created with any other tools I am aware of.Many people consider it evil to return a Data Set from a web service, but it can be a good idea, especially if you are certain that only .
NET consumers will ever need to access your web service.And reading the Data Reader actually consumed the row. Has Rows, you need to cast it to the implementation class that supports it. The Data Set has a Tables collection of Data Table objects, and the Data Table has a Rows collection that can be indexed to get to a particular row by number. Count property that enables the developer to determine the number of rows in any of the tables in a Data Set.