Skip to main content

Connecting Your Database

Updated this week

This guide walks you through connecting your database to BlazeSQL so you can start querying your data with natural language.

Supported Database Types

BlazeSQL supports the following databases:

  • PostgreSQL

  • MySQL

  • SQL Server

  • MariaDB

  • Oracle

  • Snowflake

  • Redshift

  • BigQuery

  • Clickhouse

  • Databricks

  • SQL Anywhere

  • Athena

Step 1: Choose Your Database Type

After signing in, click "Connect Database" from the onboarding wizard or from Settings → Databases. Select your database type from the list.

Step 2: Choose Connection Method

For most database types, you have two options:

  • Connect directly: BlazeSQL connects to your database and can run live queries. This is the recommended approach for the full experience.

  • Copy/paste column names: If you can't or don't want to provide direct access, you can paste your table and column names. BlazeSQL will generate SQL queries for you to run manually.

Step 3: Enter Connection Details

For a direct connection, you'll need:

  • Host: Your database server address (e.g., db.example.com or an IP address)

  • Port: The port your database listens on (default ports are pre-filled for each DB type)

  • Matching DB name: The name of the specific database on your server

  • Username: A database user with read access

  • Password: The password for that user

Some database types have special requirements:

  • Snowflake: Use your account identifier as the host (e.g., xy12345.us-east-1). Optionally specify a warehouse. Supports key pair authentication.

  • BigQuery: Upload your service account JSON key file instead of entering host/port/credentials.

  • Databricks: Enter your workspace URL as host, HTTP path, and an access token.

  • Athena: Enter your AWS access key ID, secret key, region, and S3 output location.

  • SQL Server: On the desktop app for Windows, you can use Windows Authentication instead of entering a username and password. This option is only available on the desktop version.

IP Whitelisting

If your database is behind a firewall, you'll need to whitelist BlazeSQL's IP address so it can connect:

BlazeSQL IP Address: 35.192.145.209

How to whitelist depends on your hosting provider:

  • AWS RDS: Add an inbound rule to your RDS security group allowing TCP traffic from 35.192.145.209/32 on your database port.

  • Google Cloud SQL: Go to your Cloud SQL instance → Connections → Authorized Networks → Add 35.192.145.209.

  • Azure SQL: Go to your server's Networking settings → Add a firewall rule with start and end IP 35.192.145.209.

  • Supabase: See our dedicated Supabase connection guide.

  • Other providers: Add 35.192.145.209 to your database's allowed IP list or firewall rules.

Note: IP whitelisting only applies to the web app. The desktop app connects directly from your device, so you whitelist your own IP instead.

Connecting to a Database That Isn't Remotely Accessible

If your database is on a private network and not accessible from the internet, you have a few options:

Option 1: Use the Desktop App on the Same Network

Install the BlazeSQL Desktop app on a device that's on the same network as your database (or on the database server itself). The desktop app connects directly from your device, so no external access is needed. This also keeps all query results completely local.

Option 2: SSH Tunnel (Web App)

If you prefer to use the web app, you can connect through an SSH tunnel. This lets BlazeSQL's servers reach your private database through an intermediary SSH server that has access to both the internet and your database network.

Click "+ SSH tunnel" in the connection form and provide:

  • SSH Host: The address of your SSH bastion/jump server

  • SSH Port: Usually 22

  • SSH Username: Your SSH user

  • SSH Key or Password: Authentication for the SSH connection

BlazeSQL will tunnel through the SSH server to reach your database securely. This is commonly used with private databases on AWS, GCP, or Azure that sit in a private subnet behind a bastion host.

Note: SSH tunnels are only available on the web app.

Option 3: Forward with ngrok

If you don't have an SSH bastion server, you can use a tool like ngrok to temporarily expose your local database port to the internet, then connect BlazeSQL to the ngrok URL. This is useful for quick testing or setups where configuring SSH isn't practical.

Step 4: Select Tables

After connecting, BlazeSQL will fetch your database schema and show you a list of tables. Only select the tables you need — this keeps the AI focused and improves query accuracy. You can always add or remove tables later from the database management screen.

Extract Category Values (Optional)

During setup, you'll see an option to "Extract category values". When enabled, BlazeSQL will sample distinct values from categorical columns (e.g., status fields, country names, product types). This helps the AI understand your data vocabulary and write more accurate queries. This is optional and can be toggled on or off at any time.

Privacy Note

BlazeSQL only imports metadata (table names, column names, data types) — not your actual data rows. Query results are only stored temporarily for display purposes (web app) or kept entirely local (desktop app). See our Data Privacy & Security article for full details.

Troubleshooting

If your connection fails, check these common issues:

  • Connection timed out: Make sure BlazeSQL's IP (35.192.145.209) is whitelisted in your firewall/security group, and that your database is accessible on the specified port.

  • Authentication failed: Double-check your username and password. Ensure the user has at least read permissions on the target database.

  • Database not found: Verify the "Matching DB name" matches the exact name of the database on your server (case-sensitive for some databases).

  • SSL/TLS errors: Some databases require SSL. Check your database provider's documentation for connection requirements.

  • SSH tunnel errors: Verify your SSH credentials and that the bastion host can reach the database server on the internal network.

  • "No tables found": Ensure your database user has permission to read the schema/information_schema of the target database.

Still having trouble? Reach out via the chat widget — we're happy to help you get connected.

Did this answer your question?