You must Sign In to post a response.
  • Category: ASP.NET

    ODBC and OLEDB - difference

    hi,
    can anybody say the difference between ODBC and OLEDB.....and, y and where v use dz ODBC connection in .net?????
  • #256206
    ODBC-it is designed for connecting to relational databases.
    However, OLE DB can access relational databases as well as nonrelational databases.

    There is data in your mail servers, directory services, spreadsheets, and text files. OLE DB allows SQL Server to link to these nonrelational database systems. For instance, if you want to query, through SQL Server, the Active Directory on the domain controller, you couldn't do this with ODBC, because it's not a relational database. However, you could use an OLE DB provider to accomplish that.

    In summary, The key difference between OLE DB and ODBC is that OLE DB can provide connection to data stored in non-relational format.


    OLE DB ODBC

    Retrieving data one Not supported ( Supported
    page field item at a time requires Microsoft Query) Supported

    Reconnecting to a
    moved data source Supported Notsupported

    Creating parameter Not supported Supported
    queries

    Editing queries Can be done manually Can be done in Query
    in a dialog box

    -----------------

    ODBC is Open Data Base Connectivity, which is a connection method to data sources and other things. It requires that you set up a data source, or what's called a DSN using an SQL driver or other driver if connecting to other database types. Most database systems support ODBC.

    OLE is Object Linking and Embedding. OLEDB is partly distinguished from OLE itself, now called "automation".

    OLEDB is the successor to ODBC, a set of software components that allow a "front end" such as GUI based on VB, C++, Access or whatever to connect with a back end such as SQL Server, Oracle, DB2, mySQL etal. In many cases the OLEDB components offer much better performance than the older ODBC.

    OLEDB is a different type of data provider that came about with MS's Universal Data Access in 1996 and does not require that you set up a DSN. It is commonly used when building VB apps and is closely tied to ADO. It works with COM, and DCOM as of SQL 7.0.

  • #256221
    ODBC is Open Data Base Connectivity, which is a connection method to data sources and other things. It requires that you set up a data source, or what's called a DSN using an SQL driver or other driver if connecting to other database types. Most database systems support ODBC.

    OLE is Object Linking and Embedding. OLEDB is partly distinguished from OLE itself, now called "automation".

    OLEDB is the successor to ODBC, a set of software components that allow a "front end" such as GUI based on VB, C++, Access or whatever to connect with a back end such as SQL Server, Oracle, DB2, mySQL etal. In many cases the OLEDB components offer much better performance than the older ODBC.

    OLEDB is a different type of data provider that came about with MS's Universal Data Access in 1996 and does not require that you set up a DSN. It is commonly used when building VB apps and is closely tied to ADO. It works with COM, and DCOM as of SQL 7.0.

  • #265875
    ODBC-it is designed for connecting to relational databases.
    However, OLE DB can access relational databases as well as nonrelational databases.

    There is data in your mail servers, directory services, spreadsheets, and text files. OLE DB allows SQL Server to link to these nonrelational database systems. For instance, if you want to query, through SQL Server, the Active Directory on the domain controller, you couldn't do this with ODBC, because it's not a relational database. However, you could use an OLE DB provider to accomplish that.

    In summary, The key difference between OLE DB and ODBC is that OLE DB can provide connection to data stored in non-relational format.


    OLE DB ODBC

    Retrieving data one Not supported ( Supported
    page field item at a time requires Microsoft Query) Supported

    Reconnecting to a
    moved data source Supported Notsupported

    Creating parameter Not supported Supported
    queries

    Editing queries Can be done manually Can be done in Query
    in a dialog box



    Thanks & Regards
    G.Renganathan
    Nothing is mine ,Everything is yours!!!

  • #267899
    ODBC stands for Open Database Connectivity. The ODBC call-level interface specification was created by Microsoft in 1992 as a way to standardize program-to-SQL data communication. Before ODBC, application programmers had to use a different set of API calls for every type of database. By creating a standard interface, programmers could write one set of code (for the most part) that would work with any ODBC-compliant database. ODBC was quickly embraced by most major database vendors and became a de facto standard. Notice that this cooperation happened when Microsoft was not a very large company.

    OLE DB originally stood for Object Linking and Embedding for Databases, but now the acronym just means a COM-based interface to a wide range of data sources. OLE DB is sometimes written as OLEDB or OLE-DB. OLE DB came into being in the mid 1990s through an evolution and merging of several Microsoft technologies. The idea of OLE DB is to provide programmers with a consistent interface to many different types of data, including SQL databases, Excel spreadsheets, and so on.

    Please rate this post, if it is useful for you.

    Thanks & Regards
    Ashok

  • #272143
    ODBC is Open Data Base Connectivity, which is a connection method to data sources and other things. It requires that you set up a data source, or what's called a DSN using an SQL driver or other driver if connecting to other database types. Most database systems support ODBC.

    OLE is Object Linking and Embedding. OLEDB is partly distinguished from OLE itself, now called "automation".

    OLEDB is the successor to ODBC, a set of software components that allow a "front end" such as GUI based on VB, C++, Access or whatever to connect with a back end such as SQL Server, Oracle, DB2, mySQL etal. In many cases the OLEDB components offer much better performance than the older ODBC.

    OLEDB is a different type of data provider that came about with MS's Universal Data Access in 1996 and does not require that you set up a DSN. It is commonly used when building VB apps and is closely tied to ADO. It works with COM, and DCOM as of SQL 7.0.

    Please rate this post, if it is useful for you.

    Thanks & Regards
    Ashok

  • #272146
    OLE DB and ODBC are both specifications created by Microsoft to address universal data access. Each is intended
    as an industry standard that will make access between one vendor’s data store and another vendor’s data consumer
    seamless.
    Microsoft’s definition of OLE DB is
    a strategic system-level programming interface to data across the organization. OLE DB
    is an open specification designed to build on the success of ODBC by providing an open
    standard for accessing all kinds of data.
    And the definition of ODBC is
    an industry standard and a component of Microsoft® Windows® Open Services
    Architecture (WOSA). The ODBC interface makes it possible for applications to access
    data from a variety of database management systems (DBMSs). ODBC permits
    maximum interoperability—an application can access data in diverse DBMSs through a
    single interface. Furthermore, that application will be independent of any DBMS from
    which it accesses data. Users of the application can add software components called
    drivers, which create an interface between an application and a specific DBMS.
    The two primary differences between the two are
    · OLE DB is a component based specification and ODBC is a procedural based specification
    · SQL is the core of accessing data using ODBC but just one of the means of data access through OLE DB
    · ODBC is constrained to relational data stores; OLE DB supports all forms of data stores (relational,
    hierarchical, etc)

    Please rate this post, if it is useful for you.

    Thanks & Regards
    Ashok

  • #272150
    In general, OLE DB provides a richer and more flexible interface for data access because it is not tightly bound to a
    command syntax (like SQL in the case of ODBC). As Microsoft points out:
    Whereas ODBC was created to access relational databases, OLE DB is designed for
    relational and non-relational information sources, including mainframe ISAM/VSAM
    and hierarchical databases; e-mail and file system stores; text, graphical, and
    geographical data; custom business objects; and more.
    ODBC on the other hand is a more established interface because it has been around longer; there are proven drivers
    and applications available in the market place. OLE DB is creating a better known presence, but consumer support is
    probably still considered limited. With the release of Windows 2000 Professional, OLE DB will be installed as part
    of the operating system. In Microsoft Office2000 all member applications will be OLE DB consumers. When these
    two major products ship, OLE DB will be much more ensconced in the marketplace.

    Please rate this post, if it is useful for you.

    Thanks & Regards
    Ashok


  • This thread is locked for new responses. Please post your comments and questions as a separate thread.
    If required, refer to the URL of this page in your new post.