Skip to main content
The Azure SQL connector talks to Microsoft’s managed SQL Server (Azure SQL Database, Azure SQL Managed Instance) over the standard TDS protocol with TLS. Available on Enterprise plans.

​
What Summand needs

A SQL login with read-only access to the schemas and tables you intend to analyze:
  • SELECT on the target tables
  • VIEW DEFINITION on the schemas (for catalog discovery)
  • Standard SQL INFORMATION_SCHEMA access
Summand never executes writes, never reads system tables outside INFORMATION_SCHEMA, and never executes user-supplied SQL.

​
Network access

Summand connects from two fixed egress IP addresses (visible in Settings → Connectivity). Allowlist them on the Azure SQL server’s firewall (Networking → Firewall and virtual networks). Summand reaches the server over its public endpoint. Private Link and peering are not supported, so a server with no public endpoint can’t be connected.

​
Setup

1

Create a read-only login

Use a long random password (32+ characters). Summand stores it encrypted in AWS Secrets Manager.
2

Add the connector

From Connectors → Add connector → Azure SQL, provide:
  • Server (e.g. <your-server>.database.windows.net)
  • Port — usually 1433
  • Database name
  • Username and password from the previous step
Click Test connection.
3

Pick tables and configure datasets

Same as any other database connector — Summand discovers the schemas you can read, you toggle on the tables to analyze, and you set targets per dataset.

​
Authentication

Summand uses SQL authentication (username + password). Microsoft Entra ID and managed-identity authentication are not supported.

​
Performance

Azure SQL connections honor the standard SQL Server query plan — Summand’s curation step issues straightforward SELECT * against the table. For very large tables, create a database view that pre-filters or samples and point Summand at the view.

​
Removing a connector

Deleting a connector starts a background job that deletes its datasets, their stored data and the connector’s stored credentials. Re-creating it with the same credentials works, but analysis history is not restored.