In modern technology, there is a clear need to reuse objects and let the user configure each object once and repeatedly use it over and over again.
This is the basic assumption of the “Connection” configuration in Totango Customer Data Hub.
Connection to a data source is usually done by Ops or Data teams, and the main idea is that it will be configured once and you can reuse the same connection for several integrations.
Important note, the Data Warehouse integration family is a closed system, therefore, the data source connectors which are created can be re-used for onlyData Warehouse integrations and not for other integration families.
Topics covered in this article:
- Creating Data Warehouse Connections
- Configuring MySQL Connection
- Configuring Amazon Redshift Connection
- Configuring Snowflake Connection
- Configuring PostgreSQL Connection
- Configuring MSSQL Server Connection
- Configuring Google BigQuery Connection
- Customer Data Hub Whitelisting
- SSL Encryption
Creating Data Warehouse Connections
- Go to your Totango instance and click on Global Settings > Data Management > Customer Data Hub > find the Data Warehouse source you wish to upload data from by searching or filtering connectors.
(note: you will need Totango admin privileges).
- Create a new connection (or review your existing connections)
Configuring MySQL Connection
Configuring Amazon Redshift Connection
Configuring Snowflake Connection
Configure PostgreSQL Connection
Configure MSSQL Server Connection
Configure Google BigQuery Connection
In the event that your network is behind a firewall, you will need to whitelist our servers so that we may retrieve information from your data warehouse.
Please follow the instructions in this Customer Data Hub IP Whitelisting article to configure your IP whitelist.
All data warehouse connectors support SSL encryption out-of-the-box (no need to configure anything to enable SSL encryption).
Totango connectors will use an SSL encrypted connection in case it is activated and use a non-SSL encrypted connection otherwise.
The implementation logic is as follows:
by default, SSL encryption is used during connecting, if the data warehouse server does not support SSL encryption, then the connection will using an unencrypted connection to stream data from the data warehouse.