Database connectors

When to use a database Connection

Here's when you can use a database Connection in the Etlworks Integrator:

• In a source-to-destination transformation that reads data from or writes data into the database 
• In the Flows optimized for Snowflake, Redshift, Azure Synapse Analytics, Google BigQuery, and Greenplum database. 
• In the Flows used to bulk load data into databases
• To execute any SQL
• In change-data-capture (CDC) Flows
• In the Flows that use any of the premium connectors, such as HubSpot, Marketo, etc.

Read how to work with databases in Etlworks Integrator.

Prerequisites

The Etlworks Integrator must be able to connect to the database. If the database is behind the firewall and not exposed to the Internet, there are several options:

1. Use SSH tunnel.
2. Whitelist the IP address of the Etlworks Integrator instance. The IP address of the host app.etlworks.comis 18.188.180.116.
3. Use data integration agent running behind the firewall. 

Available connectors

The following connectors are available out-of-the-box:

Create a database Connection

To create a database Connection, open the Connections window, click +, and select Database in the left navigation bar. Select the database from the gallery. Enter the database Connection parameters.

The URL

• Driver (optional): the JDBC driver class name. When one of the predefined Connection types (for example, Oracle) is selected, the driver is preset.
• URL (optional): the Connection URL. You will need to replace tokens, like <host>, <port>,<database> with the actual hostname, port, and database. Some tokens include default values.

  • before: jdbc:postgresql://<host>:<port=5432>/<database>
    after:  jdbc:postgresql://localhost:5432/mydb
    

If needed, you can use the tokens {user} and {password} to pass non-standard credentials for the username and password. For example, to connect to Google BigQuery you will need to provide a service account email and path to a secret key file. Example: OAuthServiceAcctEmail={user};OAuthPvtKeyPath={password}.

The URL can include advanced options, such as enabling SSL, etc. Please visit the database vendor website for more information.

Alternatively to URL

• Host: the database host or IP address.
• Port: the port.
• Database: the database name.

Authentication

• User: username.
• Password: password.

Other parameters

• Auto Commit: Connections with Auto Commit set to Yes commit the transaction on each executed SQL statement. Set this flag to Yes if you expect a very high volume of transactions or are planning to execute DDL statements.
• Run at Connect: the SQL statements to run each time a Connection to the database is established.

• You can run multiple ; separated SQL statements.

• Other Parameters: enter optional parameters as key=value pairs. Refer to the database vendor documentation for more information. 

Handle metadata

• Always enclose table/column names in double quotes: if this option is enabled, the system will always enclose table and column names in double-quotes. Otherwise, only names that contain spaces or start with numbers will be enclosed. Read how to handle table and column names with spaces and special characters.
• All columns are nullable: it this option is enabled all columns will be created as nullable when the flow will be creating or altering the table. The default behavior is to inherit the nullable flag from the source table.
• Varchar Field Size Multiplier: the value of this field, if greater than 1, will be used to multiple the default size of the VARCHAR-like columns (except CHAR) when automatically creating the destination table. 
• Current Database and Schema only: if this option is enabled, the system will populate tables and views for the current database and schema only. For databases with a lot of tables and views, it can greatly reduce the time needed to show the objects in Etlworks Explorer and when configuring the mapping.
• Open connection when needed: if this open is enabled ETL engine defers opening the Connection to the moment when it is requested by the ETL Flow. Read more. 
• Override Create Table SQL: by default system automatically generates an SQL for creating a new table if it does not exist. You can override the default SQL by providing a JavaScript in which the input is a variable sql (which contains automatically generated SQL) and the output is a new create table SQL. Read more. 

Fetch size, max records, max field size

Our ETL engine is written in Java and uses JDBC protocol to connect to the databases. Parameters below can be used to fine-tune the performance of the database driver.

• Fetch Size

In JDBC, the setFetchSize(int) method is very important to performance and memory-management within the JVM as it controls the number of network calls from the JVM to the database and correspondingly the amount of RAM used for ResultSet processing. Many JDBC drivers (for example Oracle) by default enforce the fetch size while some others (for example MySQL and Redshift) do not. The Fetch Size field can be used to set the maximum number of records that will be retrieved in one database call, thus limiting the memory consumption within the JVM.

You can override the Fetch Size  set at the Connection level by setting it at the transformation level.

• Max Records

By default, our ETL engine extracts all the records from the source, limited only by the source query or filter conditions. You can use this field to set the upper limit on the total number of records that can be extracted from the source.

You can override the Max Records set at the Connection level by setting it at the transformation level.

• Max Field Size

This parameter sets the limit for the maximum number of bytes that can be returned for character and binary column values in a ResultSet object produced by this Statement object. This limit applies only to BINARY, VARBINARY, LONGVARBINARY, CHAR, VARCHAR, NCHAR, NVARCHAR, LONGNVARCHAR, and LONGVARCHAR fields. If the limit is exceeded, the excess data is silently discarded. For maximum portability, use values greater than 256.

Connect to a database over SSH tunnel

A database that sits behind a firewall cannot be accessed directly from a client on the other side of the firewall, but it can often be accessed through an SSH tunnel. The firewall must be configured to accept SSH Connections, and you also need to have an account on the SSH host for this to work.

Use an actual database hostname and port when configuring the URL for the database Connection. Etlworks Integrator will automatically replace them with the localhost and the available port.

If you need to access a database that can only be accessed via an SSH tunnel, you need to specify additional information in the Connect over SSH tunnel section of the database Connection screen.

• SSH Host: the name or IP address for the host accepting SSH Connections.
• SSH Port:  the port accepting SSH Connections. The default value is 22.
• SSH User: the user name.
• SSH Password: the optional password.
• Private Key File: the private key file in the pem or ppk Format used for SSH authentication. Click the Upload/Select ssh key to manage SSH keys using GUI. You can also upload the private key file manually and use the token {app.data} as a part of the filename, for example, {app.data}/keys/secret.pem. This parameter is optional.

• SSH Passphrase: the optional passphrase (password) used together with a private key file.

Default data types of columns to VARCHAR

The automatic data type mapping mostly affects creating tables (when the table does not exist) in the destination database. The engine assumes the data type of the column in the destination table based on the data type of the column in the source and rules set for the specific ETL driver. We tweak the rules from time to time to make sure we offer the best possible match.

When configuring a database Connection, which is not one of the following: SQL Server, DB2, MySQL, PostgreSQL, Informix, Oracle, Sybase ACE, it is possible to default the data type of all columns in the table that will be automatically created to VARCHAR. The size of the VARCHAR column defaults to the maximum available for the specific database.  

Connect to Oracle

To create a Connection to an Oracle database, open the Connections window, click +, and type in oracle. Choose a Connection type from the list of available Oracle Connections.

Enter the Connection parameters.

Click here to read more about the properties that are available for an Oracle connection's URL.

Connect to MS SQL Server

To create a Connection to a Microsoft SQL Server database, open the Connections window, click +, and type in sql server. Select Microsoft SQL Server.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Microsoft SQL Server Connection's URL.

Connect to MS SQL Server using open-source JDTS driver

It is possible to connect to the MS Server server using popular JDTS JDBC driver. 

To create a Connection to a Microsoft SQL Server database, open the Connections window, click +, and type in sql server. Select Microsoft SQL Server using JTDS.

Connect to MS SQL Server using Azure Active Directory authentication

You can use Azure Active Directory (Azure AD) authentication, which is a mechanism of connecting to Azure SQL Database v12 using identities in Azure Active Directory. Use Azure Active Directory authentication to centrally manage the identities of database users and as an alternative to SQL Server authentication.

Here is the Azure Active Directory Authentication types supported by this connector:

Active directory interactive

Authenticate with your Azure credentials using an interactive authentication flow with optional multi-factor authentication.

To start the interactive flow select Active directory interactive in Authentication type and click Sign in with Microsoft.  To authenticate with the quest user, you must supply the Azure tenant ID of the account that is hosting the SQL Server (the AAD that the guest was invited to).

Active directory password

Connect using your Azure credentials directly.

MSI Authentication

If you are running SQL Server on an Azure VM, you can leverage Managed Service Identity (MSI) credentials to connect. The MSI credentials will then be automatically obtained for authentication.

Click here to read more about authentication types.

Connect to IBM DB2

To create a Connection to an IBM DB2 database, open the Connections window, click +, and type in db2. Select IBM DB2.

Enter the Connection parameters.

Click here to read more about the properties that are available for an IBM DB2 Connection's URL.

Connect to IBM AS400

To create a Connection to an IBM AS400 database, open the Connections window, click +, and type in as400. Select IBM AS400.

Enter the Connection parameters.

Click here to read more about the properties that are available for an  IBM AS400 Connection's URL.

Connect to PostgreSQL

To create a Connection to a PostgreSQL database, open the Connections window, click +, and type in postres. Select PostgresSQL.

Enter the Connection parameters.

Click here to read more about the properties that are available for a PostgreSQL Connection's URL.

Secure PostgreSQL Connections with SSL

To connect to the PostgreSQL database with SSL, you will need a server certificate, a client certificate, and a private key for the client certificate. In most cases, they will be provided as pem files.

• server-ca.pem: server certificate.

• client-cert.pem: client certificate.

• client-key.pem: private key.

The server and the client certificates can be used as is (as pem files) but the private key must be PKCS8 and stored in DER Format.

You can convert client-key.pem to the PKCS8 with openssl:

openssl pkcs8 -topk8 -inform PEM -outform DER -in client-key.pem -out postgresql.pk8 -nocrypt

Once you have the certificates and the private key, you can upload them into the Server Storage.

It is recommended to create a folder under the Server Storage, for example, postgres-certificates, and upload files into this folder.

Once files have been uploaded, you can modify the JDBC URL for the PostgreSQL Connection as below:

jdbc:postgresql://host:5432/database?ssl=true&sslfactory=org.postgresql.ssl.jdbc4.LibPQFactory&sslmode=require&sslrootcert={app.data}postgres-certificates/server-ca.pem&sslcert={app.data}postgres-certificates/client-cert.pem&sslkey={app.data}postgres-certificates/postgresql.pk8

Host, port, database name, names of the certificates, and the private key file, as well as the name of the folder with the certificates, must be replaced on actual.

Connect to Greenplum

To create a Connection to a Greenplum database, open the Connections window, click +, and type in grenplum. Select Greenplum.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Greenplum Connection's URL. Note that we are using a standard Postgres JDBC driver to connect to the Greenplum database.

Connect to Vertica

To create a Connection to a Vertica database, open the Connections window, click +, and type in vertica. Select Vertica.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Vertica Connection's URL. 

Connect to MySQL

To create a Connection to a MySQL database, open the Connections window, click +, and type in mysql. Select MySQL.

Enter the Connection parameters.

Click here to read more about the properties that are available for a MySQL Connection's URL.

Secure MySQL Connections with SSL

To connect to the MySQL database with SSL you will need a server certificate, a client certificate, and a private key for the client certificate. In most cases, they will be provided as pem files.

• server-ca.pem: server certificate.

• client-cert.pem: client certificate.

• client-key.pem: private key.

Step 1. Import the certificate authority (server) certificate into a Java keystore (JDK is required to use keytool).

keytool -import -file server-ca.pem -keystore truststore -storepass {password}

Step 2. Create a PKCS12 file from an existing signed client certificate and its private key with openssl.

penssl pkcs12 -export -in client-cert.pem -inkey client-key.pem -out client.p12 -CAfile server-ca.pem -password pass:{password}

Step 3. Import the combined certificate and private key into the keystore.

keytool -importkeystore -deststorepass {password} -destkeystore keystore -srckeystore client.p12 -srcstoretype PKCS12 -srcstorepass {password}

Once you have the truststore and keystore files, you can upload them into the Server Storage.

It is recommended to create a folder under the Server Storage, for example, mysql-certificates, and upload files into this folder.

Once files have been uploaded, you can modify the JDBC URL for the MySQL Connection as below:

jdbc:mysql://host:3306/database?useSSL=true&requireSSL=true&verifyServerCertificate=true&clientCertificateKeyStorePassword=password&clientCertificateKeyStoreType=JKS&clientCertificateKeyStoreUrl=file://{app.data}mysql-certificates/keystore.jks&trustCertificateKeyStorePassword=password&trustCertificateKeyStoreType=JKS&trustCertificateKeyStoreUrl=file://{app.data}mysql-certificates/truststore.jks

Host, port, database name, names of the truststore and keystore files, the password, as well as the name of the folder with the certificates must be replaced on actual.

Connect to MariaDB

To create a Connection to a MariaDB database, open the Connections window, click +, and type in mariadb. Select MariaDB.

Enter the Connection parameters.

Click here to read more about the properties that are available for a MariaDB Connection's URL.

Connect to Informix

To create a Connection to an Informix database, open the Connections window, click +, and type in informix. Select one of the available Informix Connection types.

Enter the Connection parameters.

If Informix is using the DB2 driver, the Connection type is selected, and the following properties are available for an Informix Connection's URL.

Otherwise, the following link details the URL properties that are available.

Connect to Sybase ASE

To create a Connection to a Sybase ASE database, open the Connections window, click +, and type in sybase. Select Sybase ASE.

Enter the Connection parameters.

The following link details the properties that are available for a Sybase ASE Connection's URL.

Connect to Snowflake

To create a Connection to a Snowflake database, open the Connections window, click +, and type in snowflake. Select Snowflake.

Enter the connection parameters.

Optionally enter Stage name. Stage refers to the location where your data files are stored for loading into Snowflake. A stage name can also be configured at the Flow level.  

Click here to read more about the properties that are available for a Snowflake Connection's URL.

Read how to work with Snowflake in Etlworks Integrator.

Connect to Snowflake using External OAuth with Azure Active Directory

Step 1. Configure Microsoft Azure AD for External OAuth.

Step 2. Set Authentication type to OAuth with Azure Active directory and User to External OAuth User.

Step 3. Set Client ID and Client Secret to client ID and secret of the Azure AD app created in step 1, set Tenant ID to your Azure Tenant ID, and set OAuth scope to the identifier (app ID URI) of the resource you want, affixed with the .default suffix.

Connect to Azure Synapse Analytics

To create a Connection to an Azure Synapse Analytics database, open the Connections window, click +, and type in synapse. Select Azure Synapse Analytics .

Enter the Connection parameters.

Click here to read more about the properties that are available for a Connection's URL.

Read how to work with Azure Synapse Analytics in Etlworks Integrator.

Connect to Azure Synapse Analytics using Azure Active Directory authentication

You can use Azure Active Directory (Azure AD) authentication, which is a mechanism of connecting to Azure Synapse Analytics using identities in Azure Active Directory. Use Azure Active Directory authentication to centrally manage identities of database users and as an alternative to SQL Server authentication.

Here is the Azure Active Directory Authentication types supported by this connector:

• Active directory password: connect using your Azure credentials directly.
• Active directory interactive: authenticate with your Azure credentials using an interactive authentication flow with optional multi-factor authentication. To start the interactive flow click Sign in with Microsoft. 
• MSI Authentication: if you are running SQL Server on an Azure VM, you can leverage Managed Service Identity (MSI) credentials to connect. The MSI credentials will then be automatically obtained for authentication.

Click here to read more about authentication types.

Connect to Amazon RDS

Amazon RDS is a fully managed database service. The following RDS connectors are available in Etlworks Integrator:

• Amazon Aurora
• PostgreSQL
• MySQL
• Oracle
• Microsoft SQL Server

Connect to Amazon Aurora PostgreSQL

Amazon Aurora PostgreSQL is essentially a fully-managed PostgreSQL cluster that is available on AWS. Use the following guidelines to configure an Aurora PostgreSQL cluster.

To create a Connection to an Amazon Aurora PostgreSQL database, open the Connections window, click +, and type in aurora. Select Amazon Aurora PostgreSQL .

Enter the Connection parameters.

Click here to read more about the properties that are available for an Amazon Aurora PostgreSQL Connection's URL.

Connect to Amazon Aurora MySQL

Amazon Aurora MySQL is essentially a fully-managed MySQL cluster that is available on AWS. Use the following guidelines to configure an Aurora MySQL cluster.

To create a Connection to an Amazon Aurora MySQL database, open the Connections window, click +, and type in aurora. Select Amazon Aurora MySQL.

Enter the Connection parameters.

Click here to read more about the properties that are available for an Amazon Aurora MySQL Connection's URL.

Connect to Amazon Redshift

Amazon Redshift is a fully-managed data warehouse that is available on AWS.

To create a Connection to an Amazon Redshift database, open the Connections window, click +, and type in redhsift. Select Amazon Redshift.

Enter the Connection parameters.

Click here to read more about the properties that are available for an Amazon Redshift Connection's URL.

Read how to work with Amazon Redshift in Etlworks Integrator.

Connect to Amazon Athena

Amazon Athena is an interactive query service that makes it easy to analyze data directly in Amazon Simple Storage Service (Amazon S3) using standard SQL. With a few actions in the AWS Management Console, you can point Athena at your data stored in Amazon S3 and begin using standard SQL to run ad-hoc queries and get results in seconds.

Read about Amazon Athena.

To create a Connection to an Amazon Athena database, open the Connections window, click +, and type in athena. Select Amazon Athena.

Enter the Connection parameters.

Click here to read more about the properties that are available for an Amazon Athena Connection's URL.

Important

To ensure that you can connect to the Amazon Athena from Etlworks Integrator, add the athena:GetQueryResultsStream policy action to the list of policies for Athena. For an example policy, see AWSQuicksightAthenaAccess Managed Policy. Additionally, ensure that port 444 is open to outbound traffic.

Read how to create objects and query data from Amazon Athena.

Connect to Microsoft Access

To create a Connection to a Microsoft Access database, open the Connections window, click +, and type in teradata. Select Microsoft Access.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Microsoft Access Connection's URL.

Connecting to Teradata

To create a Connection to a Teradata database, open the Connections window, click +, and type in teradata. Select Teradata.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Teradata Connection's URL.

Connect to Apache Hive

The Apache Hive ™ data warehouse software facilitates reading, writing, and managing large datasets residing in distributed storage using SQL. A JDBC driver is provided to connect users to Hive.

Enter the Connection parameters.

Click here to read more about the properties that are available for an Apache Hive Connection's URL.

Connect to Google BigQuery

Google BigQuery is not a typical relational database (it is actually a service), but Google has partnered with third-party companies to provide a JDBC driver that leverages the power of BigQuery's Standard SQL.

To create a Connection to Google BigQuery, open the Connections window, click +, and type in bigquery. Select Google BigQuery.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Google BigQuery Connection's URL.

Google BigQuery Driver supports the following authentication methods:

• OAuth2
• Google service account 

This guide explains how to create a new Google service account.

When creating a new service account, two parameters are important:

• A Google service account email.

• The secret key associated with the account. The key can be downloaded in the JSON or P12 Format.

Connect to Derby

Derby (Java DB) is a compact and embeddable database implemented entirely in Java and available under the Apache License, Version 2.0.

To create a Connection to a Derby database, open the Connections window, click +, and type in derby. Select Client Java DB (Derby).

Enter the Connection parameters.

Click here to read more about the properties that are available for a Derby Connection's URL.

Connect to SQLite

SQLite is available in Etlworks Integrator as a temporary staging database.

In a dedicated instance, it is also possible to create a Connection to the actual, not temporary (in memory), SQLite database.

Step 1. Open the Connections window, click +, and type in sqlite. Select SQLite.

Step 2. Enter the Connection URL as described here.

Step 3. If needed, enter a user name and password.

Connect to Neo4j

Neo4j is a graph database management system developed by Neo4j, Inc. Described by its developers as an ACID-compliant transactional database with native graph storage and processing, is available in a GPL3-licensed open-source community edition, with online backup and high availability extensions licensed under a closed-source commercial license. Neo also licenses Neo4j with these extensions under closed-source commercial terms.

To create a Connection to a Neo4j database, open the Connections window, click +, and type in neo4j. Select Neo4j.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Neo4j Connection's URL.

Connect to Elasticsearch

Elasticsearch provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.

To create a Connection to an Elasticsearch, open the Connections window, click +, and type in elasticsearch. Select one of the available Elasticsearch connectors:

Elasticsearch Legacy

This is a connector for older versions of the Elasticsearch (up to 6.x). 

Click here to read more about the properties that are available for an Elasticsearch Legacy Connection's URL.

Suggested Readings:

• How to configure the Connection
• How to insert and query data from Elasticsearch

Elasticsearch SQL

This is a connector from the creators of Elasticsearch.

The Elasticseach SQL connector requires a platinum subscription to the Elastic Stack.

This connector only supports SQL commands available as a part of the Elasticsearch SQL API: SELECT, DESCRIBE TABLE, SHOW COLUMNS, SHOW TABLES, SHOW FUNCTIONS. 

Suggested Reading:

• Available URL parameters and configuration properties

Elasticsearch Premium

Etlworks Elasticsearch premium connector allows fast, real-time access to Elasticsearch data. 

Etlworks Integrator partnered with CData to provide access to the Elasticseach API using industry-standard JDBC protocol. Read about the CData Elasticsearch JDBC connector. 

Contact support@etlworks.com to enable a connector for your account.

Suggested Readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to SAP HANA

SAP HANA is a high-performance in-memory database that speeds data-driven, real-time decisions and actions. As the data foundation of SAP’s Business Technology Platform, it provides advanced analytics on multimodel data, on-premise, and in the cloud.

To create a Connection to a SAP HANA database, open the Connections window, click +, and type in hana. Select SAP HANA.

Suggested reading:

• Connection parameters

Connect to DynamoDB

Amazon DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale. It's a fully managed, multi-region, multi-master, durable database with built-in security, backup and restores, and in-memory caching for internet-scale applications. DynamoDB can handle more than 10 trillion requests per day and can support peaks of more than 20 million requests per second.

Etlworks DynamoDB premium connector allows fast, real-time access to DynamoDB data. 

Etlworks Integrator partnered with CData to provide access to DynamoDB using industry-standard JDBC protocol. Read about the CData DynamoDB JDBC connector. 

To create a Connection to a DynamoDB database, open the Connections window, click +, and type in dynamodb. Select DynamoDB.

Suggested readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to HBase

Use Apache HBase™ when you need random, real-time read/write access to your Big Data. This project's goal is the hosting of very large tables, billions of rows X millions of columns, atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable: A Distributed Storage System for Structured Data by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, Apache HBase provides Bigtable-like capabilities on top of Hadoop and HDFS.

Etlworks HBase premium connector allows fast, real-time access to HBase data. 

Etlworks Integrator partnered with CData to provide access to HBase using industry-standard JDBC protocol. Read about the CData HBase JDBC connector. 

To create a Connection to an HBase database, open the Connections window, click +, and type in hbase. Select HBase.

Suggested readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to Cosmos DB

Azure Cosmos DB is a fully managed NoSQL database service for modern app development. Get guaranteed single-digit millisecond response times and 99.999-percent availability, backed by SLAs, automatic and instant scalability, and open-source APIs for MongoDB and Cassandra. Enjoy fast writes and reads anywhere in the world with turnkey multi-master global distribution.

Etlworks Cosmos DB premium connector allows fast, real-time access to Cosmos DB data. 

Etlworks Integrator partnered with CData to provide access to Cosmos DB using industry-standard JDBC protocol. Read about the CData Cosmos DB JDBC connector. 

To create a connection to a Cosmos DB database, open the Connections window, click +, and type in cosmos. Select Cosmos DB.

Suggested readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to Cassandra

The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance. Linear scalability and proven fault tolerance on commodity hardware or cloud infrastructure make it the perfect platform for mission-critical data. Cassandra's support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages.

Etlworks Cassandra premium connector allows fast, real-time access to Cassandra data. 

Etlworks Integrator partnered with CData to provide access to Cassandra using industry-standard JDBC protocol. Read about the CData Cassandra DB JDBC connector. 

To create a Connection to a Cassandra database, open the Connections window, click +, and type in cassandra. Select Cassandra.

Suggested readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to Btrieve

Btrieve is a transactional database (navigational database) software product. It is based on Indexed Sequential Access Method (ISAM), which is a way of storing data for fast retrieval.

Etlworks Btrieve premium connector allows fast, real-time access to Btrieve data. 

Etlworks Integrator partnered with CData to provide access to Btrieve using industry-standard JDBC protocol. Read about the CData Btrieve DB JDBC connector. 

To create a Connection to a Btrieve database, open the Connections window, click +, and type in btrieve. Select Btrieve.

Suggested readings:

• Connection URL
• Available additional parameters

Connect to Couchbase

Couchbase is an award-winning distributed NoSQL cloud database. It delivers unmatched versatility, performance, scalability, and financial value across cloud, on-premises, hybrid, distributed cloud, and edge computing deployments.

Etlworks Couchbase premium connector allows fast, real-time access to Couchbase data. 

Etlworks Integrator partnered with CData to provide access to Couchbase using industry-standard JDBC protocol. Read about the CData Couchbase DB JDBC connector. 

To create a Connection to a Couchbase database, open the Connections window, click +, and type in couchbase. Select Couchbase.

Suggested readings:

• Connection URL
• Available additional parameters
• SQL compliance

Connect to Clickhose

To create a Connection to a Clickhose database, open the Connections window, click +, and type in clickhouse. Select Clickhouse.

Enter the Connection parameters.

Click here to read more about the properties that are available for a Clickhouse Connection's URL. 

Test a database Connection

Click Test Connection on the Connection screen to test the database Connection.

Connect to a database if it is not on the list

If your database is not on the list of supported databases, you can still connect to it:

Step 1. Contact Etlworks Support so that we can add a JDBC driver for your database. Or, if you are running Etlworks Integrator on your own premises, simply drop the JDBC driver into the application server lib folder and restart the server.

Step 2. Select the Generic JDBC Connection type.

Step 3. Specify the Connection parameters.