> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summand.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure SQL

> Connect Summand to an Azure SQL Database for live, refreshable analysis.

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 a fixed set of egress IPs (visible in **Settings → Connectivity**). Allowlist them on:

* The Azure SQL **server's firewall** (Networking → Firewall and virtual networks)
* Any Azure Private Link configuration if the server is private

For servers behind Private Link with no public endpoint, Enterprise customers can request a managed peering — contact [sales@summand.com](mailto:sales@summand.com).

## Setup

<Steps>
  <Step title="Create a read-only login">
    ```sql theme={null}
    -- In master DB
    CREATE LOGIN summand_reader WITH PASSWORD = '<strong-password>';

    -- In your application database
    CREATE USER summand_reader FOR LOGIN summand_reader;
    ALTER ROLE db_datareader ADD MEMBER summand_reader;
    GRANT VIEW DEFINITION TO summand_reader;
    ```

    Use a long random password (32+ characters). Summand stores it encrypted in AWS Secrets Manager.
  </Step>

  <Step title="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**.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Authentication

Today, Summand uses **SQL authentication** (username + password). Microsoft Entra ID authentication and managed-identity authentication are on the roadmap for organizations that want to standardize on Entra credentials.

## 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 immediately revokes access and queues the curated data for deletion. Re-creating with the same credentials works, but analysis history is not restored.