What is the difference between ado and oledb

SullyTech This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Hi, This question is so surprisingly similar to this one posted on Stack Overflow. The difference between them is how they communicate with their underlying data sources. NET source talks through a. NET provider. The only reason you should use the ADO. Data Consumer An application, system driver, or user that requires access to the information contained in a database.

Data Service Provider A developer who creates stand-alone utilities services that enhance the user's or administrator's ability to use or manage the contents of a database. For example, a developer could create a query engine that allows the user to make natural language requests for information in the database.

Business Component Developer A developer who creates application modules or components that reduce the amount of coding used to create a database application. A component could be something as generic as a grid control that allows you to display a subset of the records in the database at a glance or something specific to the type of database being accessed.

NET for those developers who refuse to make the change. In addition, more database vendors provide ODBC access although this is changing now. Table We'll discuss how these differences affect your usage decisions later in this chapter. In some cases, that means the programmer has to make concessions to force the data to fit into the SQL standard.

ODBC normally requires direct programming of some type and relies heavily on the level of SQL compatibility enforced by the database vendor. In other words, the two technologies complement each other and don't act as complete replacements for each other. Unfortunately, this cross compatibility doesn't translate well to the. Yes, but you won't get the very best performance from your applications if you do.

In other words, ADO helps you to create applications quickly and enables C to take care of some of the details that you'd normally have to consider when using OLE-DB directly. ADO represents a new way to provide database access through the combination of databound ActiveX controls and five specialty classes.

You can divide the classes into two functional areas: data provider and dataset. The data provider contains classes that provide connection, command, data reader, and data adapter support. The connection provides the conduit for database communications. The command enables the client to request information from the database server. It also enables the client to perform updates and other tasks. The data reader is a one-way, read-only, disconnected method of viewing data.

The data adapter provides the real-time connection support normally associated with live data connections. So Microsoft, in addition to ODBC, has introduced other data access technologies to meet the different needs of programmers.

Note: ODBC is a process-oriented language, developed by the C language, can not be compatible with multiple languages, so it is difficult to develop, and only support limited database company, for the later Excel, etc. ODBC, open Database Connectivity, is an integral part of the database in the Microsoft Open Service Architecture Wosa,windows Open Services Architecture , which establishes a set of specifications and provides a set of standard APIs application programming interfaces for database access.

To access a database, the application must first register a data source with the ODBC Administrator, which establishes the connection between ODBC and a specific database based on information such as the database location, database type, and ODBC driver provided by the data source.

As data sources become increasingly complex, it is likely that today's applications will need to get data from different data sources, process them, and then output the processed data to another data source.

Microsoft to enable applications to access a wide variety of different numbers in a unified manner The universaldataaccess UDA architecture was proposed in UDA, with COM technology as its core, assists programmers in accessing various data sources in the enterprise.

OLE DB object link and embed are objects connected and embedded. The objects in the old DB mainly include the data source object, the stage object, the Command object, and the row group object.

The various parts of this component model are labeled with different names: Data Provider. Software components that provide data storage, small to normal text files, complex databases large to the host, or e-mail storage are examples of data providers. Some documents refer to developers of these software components as data providers. The answer is in the negative. Third, ADO. While OLE-DB allows programmers to access various types of data, it is a very good architecture, but because OLE-DB is too low-level and very complex to use, it requires the programmer to have great skill, so only a few programmers have the means to use ole-db.

This makes ole-db unable to be widely popular.