Database Reference
In-Depth Information
Classes
Description
OleDbParameter
Represents a command parameter
OleDbTransaction Represents a SQL transaction
Notice the similarity between the two data providers SqlClient and OleDb . The differences in their
implementations are transparent, and the user interface is fundamentally the same.
The ADO.NET OLE DB data provider requires that an OLE DB provider be specified in the
connection string. Table 10-4 describes some OLE DB providers.
Table 10-4. Some OLE DB Providers
Provider
Description
DB2OLEDB
Microsoft OLE DB provider for DB2
SQLOLEDB
Microsoft OLE
provider for SQL Server
DB
MicrosoftJet.OLEDB.4.0
Microsoft OLE DB provider for Access (which uses the Jet engine)
MSDAORA
Microsoft OLE DB provider for Oracle
MSDASQL
Microsoft OLE DB provider for ODBC
Understanding the ODBC Data Provider
ODBC was Microsoft's original general-purpose data access technology. It's still widely used for data
sources that don't have OLE DB providers or .NET Framework data providers. ADO.NET includes an
ODBC data provider in the namespace System.Data.Odbc .
The ODBC architecture is essentially a three-tier process. An application uses ODBC functions to
submit database requests. ODBC converts the function calls to the protocol ( call-level interface ) of a
driver specific to a given data source. The driver communicates with the data source, passing any results
or errors back up to ODBC. Obviously, this is less efficient than a database-specific data provider's direct
communication with a database, so for performance it's preferable to avoid the ODBC data provider,
since it merely offers a simpler interface to ODBC but still involves all the ODBC overhead. Table 10-5
describes some important classes in the Odbc namespace.
 
Search WWH ::




Custom Search