ADO exposes a rich subset of the OLE DB model, so many of the comparisons we've already made to OLE DB programming also apply to ADO. However, because ADO exposes only a subset of OLE DB, ADO.NET goes beyond ADO in some areas. ADO always uses all OLE DB services by default and hides the client cursor engine as an option of Recordset.
The ADO.NET object model will be familiar to ADO programmers because the names and functionality of some of the classes correspond:
ADO Connection to ADO.NET Connection
ADO Command to ADO.NET Command
ADO Recordset (default cursor type and location) to ADO.NET Data-Reader
Table 9-1 shows equivalents between the ADO and ADO.NET data models.