NET has a Connection object that we use to manage our connection to our data source. Things start to get different when we look at the ADO. In many ways, the Data Set object looks like a weird amalgam of all of the old DAO objects holding tables, relations, and columns. The Command object is used to submit SQL statements or to execute stored procedures. NET Command object accepts parameters and supports re-executing compiled commands.Sometimes the data you work with is primarily read-only and you rarely need to make changes to the underlying data source Some situations also call for caching data in memory to minimize the number of database calls for data that does not change.
Data Row/Data Row View objects implement IEditable Object and when some data in Rad Grid View is changed, the internal Currency Manager calls End Edit of current item after the current position is changed to another row. NET Data Provider for Teradata, generates Insert, Update and Delete commands for a Batch Update.But How can you associate a Transaction with CUD commands given that you have no direct control over the Command generation?Additionally, the data adapter contains command object references for SELECT, INSERT, UPDATE, and DELETE operations on the data.You will have a data adapter defined for each table in a Data Set and it will take care of all communication with the database for you.