Skip to main content

​
Overview

Emit collected data from Entegrata into any Microsoft SQL Server database — on-premise, Azure SQL Database, Azure SQL Managed Instance, or Amazon RDS for SQL Server. Destination type: SQL database

​
Before You Start

  • Ask your DBA for a service account on the target database that can write to the emission schema
  • Pick (or create) a target schema where Entegrata can create and manage tables
  • Make sure the SQL Server is reachable from Entegrata (firewall / private-link rules)

​
Required Permissions

Grant the service account:
  • SELECT, INSERT, UPDATE, DELETE on the target schema
  • CREATE TABLE, ALTER, and DROP on the target schema (so Entegrata can create staging tables, apply schema changes, and swap tables during Full Refresh)
  • VIEW DEFINITION on existing objects in the schema
Entegrata manages the lifecycle of the tables it emits — it creates, drops, and swaps them as part of normal operation. Dedicate an emission schema rather than sharing one with tables maintained by other systems.

​
Connection Details

​
string
required
SQL Server hostname or IP address.Examples: sqlserver.company.com, 10.20.30.40, my-instance.database.windows.net
​
number
TCP port. Leave blank to use the default (1433). Azure SQL Managed Instance’s public endpoint typically uses 3342.
​
string
required
Name of the target database.
​
string
required
Schema inside the database where emitted tables live. Defaults to dbo.
​
boolean
default:"true"
Encrypt the connection in transit. Enabled by default. Only disable for legacy servers that cannot negotiate encryption.

​
Authentication

Pick the method that matches how your SQL Server is configured.
Entra ID and Entra Service Principal are only available for SQL Servers hosted in Azure (Azure SQL Database, Azure SQL Managed Instance, or SQL Server running on Azure VM / Arc with Entra authentication enabled). See Azure Entra ID Authentication for the setup steps.
Standard SQL login with a username and password.
​
string
required
SQL Server login with write access to the target schema.
​
string
required
Password for the login (encrypted at rest).

​
Write Modes

  • Full Refresh — Entegrata loads all rows into a staging table and atomically swaps it with the target table. Any indexes, unique keys, and foreign keys you’ve added to the target are captured beforehand and reapplied after the swap.
  • Incremental Merge — Entegrata writes only rows that changed in the source since the last emission, using the target’s primary key to apply inserts, updates, and deletes in a single MERGE.
Entegrata picks the mode automatically on each emission — Full Refresh for the first run or when the schema changes materially, Incremental Merge for subsequent runs.

​
Naming Convention

Emitted table and column names are transformed to match the convention configured on the emitter (default: snake_case). Configure the convention per emitter to match the downstream tools consuming the replica.