Get Data Moving 1
Results 1 to 1 of 1

Thread: How do ODBC, ThinODBC and BindURL relate

  1. #1
    Join Date
    Sep 2006
    Posts
    233
    Rep Power
    10

    How do ODBC, ThinODBC and BindURL relate

    AIS offers an ODBC provider on all platforms. On Windows it is provided via the Windows ODBC driver manager while on other platforms it is provided as a CLI library for applications to use (with 3rd party driver managers or directly).

    The standard AIS ODBC provider is considered 'fat' in that it works against the local AIS query processor. Its work can be delegated (so no query processing is done locally) but still the query processor and object store are present.

    Attunity provides a 'Thin ODBC' kit for certain version of AIS which is similar to the 'fat' provider but it is lighter since the query processor, backend drivers and repository access code were eliminated. It is not recommended to use both kits on the same machine since they both use DLLs with the same name (ODNAV, NAV32 and NVBASE) and mixing them will result in errors.

    Performance wise there is no difference between the thin and fat kits. However, with the thin ODBC provider one cannot access local data sources.

    Now BindURL is a connection string option available on all native providers (ODBC fat and thin and OLEDB/ADO) that instructs the provider to access a remote machine for binding information. The BindURL format is:

    Code:
    bindUrl=[attconnect://][username:password@]host[:port][/workspace]
    The provider accesses the AIS workspace server and uses that server's binding to work with datasources.
    Last edited by DrorHarari; 07-19-2011 at 04:56 AM.
    By Dror Harari

    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •