Connectors

Databases & Data Warehouses

ODBC

Any database with an ODBC driver: run SQL, insert rows, and list schemas and tables
Signs in with
Connection details
Runs on
Cloud or On-Prem Worker
Operations
7
Ready-made triggers
0

Connect ODBC

  1. In Neblex open Connect › Connections and click New Connection.
  2. Search for ODBC and give the connection a clear name.
  3. Fill in the fields. Secret values are encrypted and never shown again.
  4. Click Test, then Create Connection.
If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.
FieldWhat to enter
DriverOptionalThe ODBC driver installed on the On-Prem Worker, exactly as it is listed there (for example IBM DB2 ODBC DRIVER). Leave empty when you use a data source name.
Data source name (DSN)OptionalA data source configured on the On-Prem Worker. When set, it is used instead of the driver.
Connection attributesOptionalThe driver's own connection keywords, separated by semicolons. Enter the user and password in their own fields.Example: HOSTNAME=db.example.com;PORT=50000;DATABASE=SAMPLE
UserOptional
PasswordOptionalSecret

Use it in a flow

  1. Open a flow, open the node library and search for ODBC.
  2. Drag it onto the canvas and choose an Operation and your connection.
  3. Map the operation's fields from earlier steps, or click Map with Matt.
  4. Use Test this step to see what it returns, then save.

To start a flow from ODBC without a ready-made trigger: a Poll for changes trigger on ODBC with your own query passes on new or changed records.

Operations

7 operations in 3 groups. Each one is a step you can add to a flow.

Connection1
Test the connectionpingConnect through the installed ODBC driver and return the database product and version.
Schema3
Describe tabledescribeTableList the columns of one table with their types, sizes, nullability, defaults and primary key.
List schemaslistSchemasList the schemas the connected user can see.
List tableslistTablesList the tables and views the connected user can see, filtered by name, schema, catalog and type.
SQL3
Execute commandexecuteRun the DML, DDL or procedure call entered in the statement editor once per record, in one transaction that commits only when every record succeeded.
Execute queryqueryRun the SQL entered in the statement editor with :name parameters bound from each record.
Insert rowsinsertRowsInsert one row per record into the table, in one transaction, sending rows in batches when the driver supports it.