Creating Your First Data Source
Step One: Create a Data Source
To get started, create a new Data Source from either the landing page or the Data Sources page.
Step Two: Select a Database Type
Next, give your Data Source a name and choose the type of database you want to connect to DataReportive. We support a wide range of SQL-based databases:
- Amazon Athena
- Azure Synapse
- BigQuery
- ClickHouse
- MySQL
- PostgreSQL
- Presto
- Amazon Redshift
- Snowflake
- SQL Server
- Timescale
- Trino
Step Three: Set Connection Parameters
After selecting your database, enter the required connection details. Before proceeding, ensure you have the necessary permissions and network access to your database. For more information, see our section on setting up access.
Host
Enter the IP address (e.g., 172.158.23.48) or hostname (e.g., yourhostname.com) of your database server.
Tip:
Your database must be accessible from the Internet for DataReportive to connect. Avoid using "127.0.0.1" or "localhost", as these refer to your local machine. Similarly, databases restricted to a local network will not be reachable.
Port
Specify the port number for your database. DataReportive will automatically suggest the default port for the selected database type.
Username
Provide the username that DataReportive should use to access your database.
Password
Enter the password for the specified username.
Database
If your server hosts multiple databases, specify the one you want to connect to. To access a different database on the same server, create a new Data Source.
Step Four: Configure SSH and SSL
For enhanced security, you can configure SSH tunneling or SSL mode when connecting to your database. Make sure you have the required credentials and certificates. For detailed instructions, see setting up access.
Each SSL option carries certain overhead based on the form of encryption and key-exchange. Therefore there is a tradeoff to be made between performance and security. The following table illustrates the risks the different SSL Mode values protect against, and what statement they make about security and overhead. For more on SSL Modes please refer to the PostgreSQL documentation.
| sslmode | Eavesdropping protection | Man-in-the-Middle protection | Statement |
|---|---|---|---|
| disable | No | No | I don't care about security, and I don't want to pay the overhead of encryption. |
| allow | Maybe | No | I don't care about security, but I will pay the overhead of encryption if the server insists on it. |
| prefer | Maybe | No | I don't care about encryption, but I wish to pay the overhead of encryption if the server supports it. |
| require | Yes | No | I want my data to be encrypted, and I accept the overhead. I trust that the network will make sure I always connect to the server I want. |
| verify-ca | Yes | Depends on CA-policy | I want my data encrypted, and I accept the overhead. I want to be sure that I connect to a server that I trust. |
| verify-full | Yes | Yes | I want my data encrypted, and I accept the overhead. I want to be sure that I connect to a server I trust, and that it's the one I specify. |
Need Help?
If you're having trouble connecting your database to DataReportive, contact us and our team will be happy to assist you.