Warehouses

Connect a data warehouse

Connect BigQuery, Snowflake, Databricks, SQL Server, Azure SQL or Microsoft Fabric, so Ahamo's AI can answer questions with your company's data.

On this page

Connect your company's warehouse once, and Ahamo's AI can answer questions with its tables in the chat, keep the answers on a dashboard, and follow the rules your admins set with datasets.

Availability. Each warehouse is a connector. Ahamo turns it on before anyone can use it, and your organisation decides which connectors its workspaces get. If a warehouse isn't listed in Connectors, it isn't on for your workspace. See Connect the tools you already use.

Warehouses you can connect

WarehouseHow Ahamo signs in
BigQueryYour Google account, in Google's sign-in window
SnowflakeA service user with a key pair
DatabricksA service principal, or a personal access key
SQL ServerA SQL login, on Azure SQL, Amazon RDS or your own server
Azure SQLA Microsoft Entra service principal
Microsoft FabricA Microsoft Entra service principal, on a warehouse or a lakehouse

Connect one

  1. Open Connectors, choose Discover and find the warehouse.
  2. Choose Connect. The dialog lists the steps to make the account Ahamo signs in with and the permissions to give it.
  3. Fill in the warehouse's details, such as its account, server or workspace address.
  4. Say what the account can do. Choose Only read when it can only read. See the next section.
  5. Paste the key or secret, give the connection a name, choose who may use it, and choose Test and connect.
  6. Wait for Connected to … It works.

BigQuery opens Google's sign-in window instead of asking for a key.

Give the account the fewest rights it needs. Each warehouse's page shows the grants to make.

Read-only connections

What a connection can do decides how Ahamo uses it:

  • Only read means Ahamo's AI runs a query without asking. Dashboards and datasets work only on a read-only connection.
  • Change data means you approve each query in a card in the chat before it runs, because SQL can change or delete data.

For Snowflake and Databricks you declare it when you connect. Ahamo doesn't read the SQL, so choose Only read only for an account that really can only read. For SQL Server, Azure SQL and Microsoft Fabric, Ahamo checks when you connect that the account can't write, and refuses one that can. For BigQuery it follows what you allow in Google's window. With View your data in BigQuery alone, the connection can only read.

Ahamo's fixed address

SQL Server, Azure SQL and Microsoft Fabric connections always reach your server from one fixed Ahamo address. Allow that address in your server's firewall, on the server's port.

When you connect SQL Server, the dialog shows the address, as in Allow … on port 1433 in your firewall. Azure SQL and Microsoft Fabric use the same address.

Ahamo connects only to servers the internet can reach. Servers reachable only on a private network are not supported.

Limits

Ahamo sets these limits on every query:

LimitValue
Run time2 minutes, then the query is stopped
Size of an answer1,000,000 rows or 25 MB, then the answer is cut and says so
Billed data per BigQuery query10 GiB. A query above it is refused and costs nothing

Queries run in your warehouse and are billed by it. Every query is in Ahamo's audit log with its SQL, and carries the id of the person who asked it, so your warehouse's own history shows it too.

Troubleshooting

The warehouse isn't in Connectors. It isn't turned on for your workspace. Ask a workspace admin or your organisation's admin.

This login can change data, so Ahamo doesn't connect with it. The account has rights that write. Give it read rights only and connect again.

Ahamo couldn't reach the server. Check the server name and port, and allow Ahamo's fixed address in the server's firewall.

A dashboard tile says the connection can change data. Dashboards don't run queries on such a connection. Connect the warehouse again as Only read.

Next steps

On this page