The first thing to do is to connect Holistics to your SQL database (usually data warehouse).
If you don't use a SQL database, please refer to this page for more information.
Creating DB User
It's a standard security practice that you should create a separate, usually read-only database user for 3rd-party services After you have set up this dedicated user, you can connect it to Holistics.
There are 2 methods to connect SQL database to Holistics:
- Direct Connection: this is the easiest method as it simply requires you to whitelist Holistics IPs.
- Reverse SSH Tunnel: If your database is behind a firewall/closed network/VPN you don't want to modify any firewall rules, you can consider setting up a reverse SSH tunnel.
Holistics currently support the following SQL databases:
- Amazon Athena
- Amazon Redshift
- Google BigQuery
- Microsoft SQL Server
(For list of features we supported for each database, click here)
For non-SQL data sources: we support Google Sheets and CSV/Excel. However, you need to have a SQL database, and use Holistics to load data from these sources into your SQL database.
I'm concerned about data security.
You can check out our Data Security policy for more information. But in short:
- We don't store your raw data, we just store metadata/connection to your database.
- We encrypt the database credentials you provided
- The connection between Holistics and your database are secure
Can I connect to a local SQL database (for testing purpose)?
Since Holistics is a cloud-based application, you will either need a public accessible IP or use a SSH reverse tunnel to connect your localhost to Holistics app.
Or you can consider using something like ngrok for testing purpose.