Difference b/w Dataset & Recordset?
-
thanks Apurva. do u thinkis this statements are correct?? a DataSet will have all the data locally. However, this is both a curse and a blessing. It means all the data will have to be fetched before any work can be done, which may increase latency and memory usage substantially. The Recordset is cached behind the scenes, so there will only be roundtrips to the server when needed to refill the cache. BTW, in .NET the equivalent of a Recordset is the SqlDataReader (or equivalent for datasources other than SQL Server). It can return multiple results, but you have to process them one by one in order. Most of the time a DataReader is the fastest method. if u know more points let me know thanks again Suketh
-
thanks Apurva. do u thinkis this statements are correct?? a DataSet will have all the data locally. However, this is both a curse and a blessing. It means all the data will have to be fetched before any work can be done, which may increase latency and memory usage substantially. The Recordset is cached behind the scenes, so there will only be roundtrips to the server when needed to refill the cache. BTW, in .NET the equivalent of a Recordset is the SqlDataReader (or equivalent for datasources other than SQL Server). It can return multiple results, but you have to process them one by one in order. Most of the time a DataReader is the fastest method. if u know more points let me know thanks again Suketh
What exactly you want to know? These things are quite correct. Dataset follows a disconnected architecture. Once you get the data from the database you are disconnected. If you again want to update the dataset with the database you again need to get connected and update it. Here[^] you will get the details of ado.net architecture.
Best Regards, Apurva Kaushal