Ado.net uses dataset for accessing the data , since the dataset is created in client side there is no need of connection at the time of working on dataset ,to the server(where the database is present), so this makes the data accessing faster mainly in the net environment.
rs:
Ado.net uses dataset for accessing the data , since the dataset is created in client side there is no need of connection at the time of working on dataset ,to the server(where the database is present), so this makes the data accessing faster mainly in the net environment.
By using template column, as
<asp:TemplateColumn>
<asp:ItemTemplate>
<asp:CheckBox></asp:CheckBox>
<asp:DropDownList></asp:DropDownList>
</asp:ItemTemplate>
</asp:TemplateColumn>
Data Reader worked as conventional Record Set of VB but Data Set Can store a complete database with all the relations and constraints.
Data Reader worked in Read only where as Data Set provide u the flexibility of Updating data also.
Data Reader worked in connected mode only, whereas Data set works in disconnected mode also.
Recordset is a collection of records returned by the query.
Dataset is merely a collection of tables.
If the RowState property of the DataRow is "Modified" then that DataRow can be treated as updated.
If dr.RowState=DataRowState.Modified then
' u r logic here
End if
ADO and ADO.NET are different in several ways:
ADO works with connected data. This means that when you access data, such as viewing and updating data, it is real-time, with a connection being used all the time. This is barring, of course, you programming special routines to pull all your data into temporary tables.
ADO.NET uses data in a disconnected fashion. When you access data, ADO.NET makes a copy of the data using XML. ADO.NET only holds the connection open long enough to either pull down the data or to make any requested updates. This makes ADO.NET efficient to use for Web applications. It's also decent for desktop applications.
ADO has one main object that is used to reference data, called the Recordset object. This object basically gives you a single table view of your data, although you can join tables to create a new set of records. With ADO.NET, you have various objects that allow you to access data in various ways. The DataSet object will actually allow you to store the relational model of your database. This allows you to pull up customers and their orders, accessing/updating the data in each related table individually.
ADO allows you to create client-side cursors only, whereas ADO.NET gives you the choice of either using client-side or server-side cursors. In ADO.NET, classes actually handle the work of cursors. This allows the developer to decide which is best. For Internet development, this is crucial in creating efficient applications.
Whereas ADO allows you to persist records in XML format, ADO.NET allows you to manipulate your data using XML as the primary means. This is nice when you are working with other business applications and also helps when you are working with firewalls because data is passed as HTML and XML.
Webmaster 20th of May 2012
Tell us what you feel about ADO.NET 2.0 Interview Questions and Answers
All comments will be published after review. No login or registration is required to post a comment on ADO.NET 2.0 Interview Questions and Answers We offer and invite you to submit your valuable comment now; Please be respectful of others when commenting. Insulting others, self-promotional comments, website promotional comments, marketing stuff, SEO Techniques, SMS-style content and off-topic comments will not be approved at this information portal.
So start sharing your thoughts regarding ADO.NET 2.0 Interview Questions and Answers
Thank you.