Connector
Generic ODBC Connector
A database without a connector of its own? If it has an ODBC driver, Rapidi can usually read and write it through the generic ODBC connection.
Rapidi's generic ODBC connection moves data to and from any database with an ODBC driver, on ODBC 1.0, 2.0, 3.0 or 3.5. It uses a DSN or the driver directly, either through RapidiConnector on your own server or straight from Rapidi's central server, which supports drivers such as Oracle and PostgreSQL.
- What it connects to
- Any database reachable through an ODBC DSN or ODBC driver.
- Which way the data moves
- Both ways. Rapidi transfers data to and from ODBC data sources.
- What you need
- The ODBC driver for your database, and the connection details: server, port, database, user ID and password.
What does this connector actually do?
| ODBC versions | ODBC 1.0, 2.0, 3.0 and 3.5. |
|---|---|
| DSN or driver | Choose 2.0 DSN, 3.0 DSN, 2.0 driver or 3.0 driver on the connection. A DSN is created and tested in the ODBC Administrator first. |
| Direction | Both ways. Rapidi transfers data to and from ODBC data sources. |
| Connection details | The DSN name or the full driver string in Server Connect, or the server, port, database, user ID and password in their own fields. Rapidi adds the parameter names and separators itself. |
| SQL schemas | Enter a schema to limit which tables are read and used. A database with several schemas gets one connection per schema. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| Where it can run | Through RapidiConnector on a server that can see the database, or directly from Rapidi's central server for supported drivers. |
What goes on your side?
There are two ways to run the connection. What changes is whether anything is installed near your database.
| What you are comparing | Through RapidiConnector | Directly from Rapidi |
|---|---|---|
| Installed on your side | RapidiConnector and the ODBC driver for your database, on the same server | Nothing. You delete the RapidiConnector from the connection |
| How Rapidi reaches the database | RapidiConnector connects out to the Rapidi service and keeps that connection open | Rapidi's central server connects to your ODBC data source |
| Drivers | The ODBC driver you install, through a DSN or used directly | Supported drivers such as Oracle and PostgreSQL, and AWS. Ask us for the exact Server Connect parameters |
| Direction of the data | Both ways | Both ways |
Which databases have a connector of their own?
Several databases have a dedicated Rapidi connection type. Generic ODBC covers the rest.
Database connector
Microsoft SQL Server
SQL Server has its own connection type, with its own setup guide.
Databases and Warehouses
Database connector
MySQL
MySQL has its own connection type, with its own setup guide.
Databases and Warehouses
Database connector
Oracle Database
Oracle has its own connection type, with its own setup guide.
Databases and Warehouses
Where do you go next?
Connectors
Every system Rapidi connects to
The full list, A to Z, with versions and how each one connects.
All connectors
Connector
REST Web Service
The generic connection for any system with a REST API, read from a JSON Schema or Swagger 2.0 description.
APIs and Protocols
Pricing
What Rapidi costs
Four plans, priced per subscription rather than per connector.
Plans
Your setup
Ask about your database
Tell us the database and its ODBC driver, and we will say plainly whether this connection covers it.
Talk to a consultant
Frequently asked questions
Which ODBC versions does Rapidi support?
ODBC 1.0, 2.0, 3.0 and 3.5. On the connection you choose 2.0 DSN, 3.0 DSN, 2.0 driver or 3.0 driver.
Can Rapidi write to an ODBC database, or only read?
Both. The generic ODBC connection transfers data to and from ODBC data sources.
Do we have to install anything?
Not always. Rapidi can connect directly from its central server to your ODBC data source, with supported drivers such as Oracle and PostgreSQL. Otherwise RapidiConnector and the ODBC driver go on a server that can see the database.
Should we use a DSN or the driver directly?
Either works. A DSN is created and tested in the ODBC Administrator on the server first. With the driver used directly, you enter the driver name and connection details on the Rapidi connection instead.
Our database uses several SQL schemas. How does that work?
Enter a schema on the connection and Rapidi reads and transfers only that schema's tables. For several schemas, create one ODBC connection for each.
How often does the data move?
On a schedule you set. The shortest interval comes from your plan, from one hour on Entry down to one minute on Unlimited.
What does the Generic ODBC connector cost?
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding an ODBC connection does not change the licence.
Does your database have an ODBC driver?
Tell us the database and where it runs, and we will tell you plainly whether the generic ODBC connection covers it.