Search our Wiki
ODBC
The following versions of generic ODBC are supported
- ODBC 1.0, 2.0, 3.0 and 3.5.
- either ODBC DSN can be used or you can use an ODBC Driver directly
You can use our Generic ODBC support either through a RapidiConnector (in which case you should install the RapidiConnector as described below and you have to install ODBC Drivers as described below) or you can let Rapidi connect directly from our central server to your ODBC data source (in which case you must delete the RapidiConnector on the Connection). When connecting directly, we support different ODBC Drivers like Oracle and PostGRE, and AWS. Please contact us regarding the exact parameters to use in the Server Connect field.
In order to connect to BigQuery, please follow the instructions from this page.
Additional installation
If you want to transfer data to/from ODBC Data Sources, you have to do the following:
- Install ODBC driver for your database on the server where the RapidiConnector is installed (if not already done).
- Create a connection for each database that you want to transfer data to/from. You can create the connection in the "ODBC Administrator" via a "DSN" connection or by using an "ODBC driver" directly.
Configuration
The fields of the Generic ODBC Data Source Card are used as follows:
- Code: The code for this Connection is assigned when the Connection id is created and cannot be changed.
- Description: Enter a short text describing this Connection. Please put in a good description here as the Code is always very generic and it's not easy to know what the connection is used for without a good description.
- ODBC Version: Specify which ODBC version you use. Choose between 2.0 DSN, 3.0 DSN, 2.0 driver or 3.0 driver. When using the DSN types, you need to create and test the DSN in the ODBC Administrator tool on the Server before you can use it here.
-
Server Connect: Enter the DSN name or the full driver name here.
When using 2.0 Driver or 3.0 Driver, you can also enter all the connection parameters in this field and then leave the next fields empty - like: "Microsoft Access Driver (*.mdb);DBQ=C:\database\NORTHWIND.MDB"
We will automatically put DRIVER= in front of the value you put in this field.
In general, you can either enter parameters in this field or use the fields below for the different parameters. You can even do a combination of some parameters here and some parameters using the fields below. - Server Name/IP: When using 2.0 Driver or 3.0 Driver and if you did not enter the SERVER= parameter on the Server Connect field above, then you can enter it here. We will automatically put SERVER= before the value you enter.
- Port: When using 2.0 Driver or 3.0 Driver and if you did not enter a specific Port in the Server Connect, you can enter it here. We will automatically put PORT= before the value you enter. This parameter is only needed if you are not using the standard port on the server side.
- Database: When using 2.0 Driver or 3.0 Driver and if you did not enter a specific DATABASE in the Server Connect, you can enter it here. We will automatically put DATABASE= before the value you enter.
- UserID: When using 2.0 Driver or 3.0 Driver and if you did not enter a specific USERID in the Server Connect, you can enter it here (if needed). We will automatically put UID= before the value you enter.
- Password: When using 2.0 Driver or 3.0 Driver and if you did not enter a specific Password in the Server Connect, you can enter it here (if needed). We will automatically put PWD= before the value you enter.
- Schema: Here you can enter the Database SQL Schema if your database is using SQL Schema's. The Schema entered here will be used to filter the tables we read design for and will also automatically be used when running transfers. If your database has several SQL Schema's you can create one ODBC Connection for each Schema.
Please Note: You should NOT put ; in the fields above, just the value. We automatically add the ; in between the parameters. Some of the parameters can be changed in the rapidi.cfg parameter file, please contact our support if needed.
Copy, Test, Activate Changes, and Read Design