Get Help

Odbc@1

Odbc@1 reads data from anything that has an ODBC driver. Needs that driver, 64-bit, installed on the machine.

Connects to

Any system that ships an ODBC driver — Databricks, for one.

Example

Name
MyOdbcData
Technology
ODBC
Provider
Odbc@1
Connection string
DSN=AERO_DWH
Data sources:
- Name: MyOdbcData
  Provider: Odbc@1
  Technology: Odbc
  Connection string: DSN=AERO_DWH

The example assumes you already have a 64-bit ODBC entry named AERO_DWH.

Connection string

A standard ODBC connection string — Key=Value pairs separated by semicolons, as System.Data.Odbc passes it to the ODBC driver manager. It names either a DSN or a driver; every other key belongs to the driver:

Key Meaning
DSN Name of a 64-bit ODBC entry configured on the machine; the entry holds everything else
Driver Name of an installed ODBC driver, for a DSN-less string; followed by that driver’s own keys (Host, Port, HTTPPath, …)
Uid, Pwd Credentials, when the driver or DSN does not hold them

The format is described in the OdbcConnection.ConnectionString reference; the keys themselves are in your driver’s documentation.

A password, or the whole string, can come from an environment variable — %NAME% is replaced with the value of NAME; see How every provider is used.

A DSN-less string

When you cannot, or do not want to, maintain an ODBC entry on the machine — a token that expires, a DSN you do not own — name the driver directly. Databricks with the Simba Spark driver:

Name
Databricks
Technology
ODBC
Provider
Odbc@1
Connection string
Driver=Simba Spark ODBC Driver;
Host=%HOST%;
Port=443;
HTTPPath=%HTTP_PATH%;
ThriftTransport=2;
SSL=1;
AuthMech=3;
Uid=token;
Pwd=%TOKEN%;

Data sources:
- Name: Databricks
  Provider: Odbc@1
  Technology: Odbc
  Connection string: >
    Driver=Simba Spark ODBC Driver;
    Host=%HOST%;
    Port=443;
    HTTPPath=%HTTP_PATH%;
    ThriftTransport=2;
    SSL=1;
    AuthMech=3;
    Uid=token;
    Pwd=%TOKEN%;

HOST, HTTP_PATH and TOKEN are environment variables. The full walk-through, including the driver install and the DSN variant, is in Test Databricks.

Settings

None beyond Connection string.

Query

One SQL statement in the dialect of the system behind the driver that returns a result set.

Prerequisites

Nothing for CAT itself — System.Data.Odbc ships with it. The ODBC driver of the system you connect to must be installed on the machine, 64-bit, and an ODBC entry, if you use one, must be a 64-bit entry too.

Limitations

Windows only today; Linux support will come when users ask for it.

Serving test and data source definitions

Odbc@1 can also serve lists of definitions: any statement that returns the columns of a test, data source or query definition works. Ready-made table scripts are in Store definitions in a database.

  • Technologies — what CAT can test, with the provider behind each.
  • Test Databricks — driver install, ODBC entry and first test, step by step.
← MySql@1
Oracle@1 →