Microsoft Data Access Components and ADO.NET

1
Microsoft Data Access Components and ADO.NET

• CIS 764 Presentation
• Somil Chandwani

2
MDAC

• With Microsoft Data Access Components (MDAC),
  developers can connect to and use data from a
  wide variety of relational and nonrelational data
  sources. You can connect to many different data
  sources using ActiveX Data Objects (ADO), Open
  Database Connectivity (ODBC), or OLE DB.

3
Current MDAC Architecture
4
ADO

• ADO ActiveX Data Objects (ADO) provides a
  high-level programming model that will continue
  to be enhanced. Although a little less
  performance than coding to OLE DB or ODBC
  directly, ADO is straightforward to learn and
  use, and it can be used from script languages,
  such as Microsoft Visual Basic Scripting Edition
  (VBScript) or Microsoft JScript.

5
OLE DB

• OLE DB OLE DB is a comprehensive set of COM
  interfaces for accessing a diverse range of data
  in a variety of data stores. OLE DB providers
  exist for accessing data in databases, file
  systems, message stores, directory services,
  workflow, and document stores. OLE DB core
  services (although not every OLE DB provider) is
  available on the 64-bit Windows operating system.

6
ODBC

• ODBC The Microsoft Open Database Connectivity
  (ODBC) interface is a C programming-language
  interface that allows applications to access data
  from a variety of Database Management Systems
  (DBMS). Applications that use this API are
  limited to accessing relational data sources
  only. ODBC is available on the 64-bit Windows
  operating system.

7
ADO.NET

• ADO.NET is an evolutionary improvement over
  traditional ADO for creating distributed,
  data-sharing applications. It is a high-level
  application-programming interface that is
  targeted at loosely coupled, n-tier,
  Internet-based applications that support
  disconnected access to data. It is a core
  component of the Microsoft .NET Framework.

8
Overview of ADO.NET 

• ADO.NET provides consistent access to data
  sources such as Microsoft SQL Server and XML, as
  well as to data sources exposed through OLE DB
  and ODBC. Data-sharing consumer applications can
  use ADO.NET to connect to these data sources and
  retrieve, manipulate, and update the data that
  they contain.

9
Design Goals for ADO.NET

• Leverage current ActiveX Data Objects (ADO)
  knowledge.
• Support the n-tier programming model.
• Integrate XML support.

10
ADO.NET Architecture
11
.NET Framework Data Providers

• .NET Framework Data Provider for SQL Server -
  Provides data access for Microsoft SQL Server
  version 7.0 or later. Uses the System.Data.SqlClie
  nt namespace.
• .NET Framework Data Provider for OLE DB - For
  data sources exposed using OLE DB. Uses the
  System.Data.OleDb namespace.
• .NET Framework Data Provider for ODBC - For data
  sources exposed using ODBC. Uses the
  System.Data.Odbc namespace.
• .NET Framework Data Provider for Oracle - For
  Oracle data sources. The .NET Framework Data
  Provider for Oracle supports Oracle client
  software version 8.1.7 and later, and uses the
  System.Data.OracleClient namespace.

12
ADO.NET DataSet 
13
What's New in ADO.NET 

• Server Enumeration
• Asynchronous Processing
• Multiple Active Result Sets (MARS)
• DataSet Enhancements
• Binary Serialization for the DataSet
• DataView Performance Improvements
• XML/XSD Enhancements

14
References

• www.msdn.microsoft.com
• en.wikipedia.org/wiki/ADO.NET
• en.wikipedia.org/wiki/Microsoft_Data_Access_Compon
  ents

15

• Questions?