Skip to content
Developer tools ⇄ Database

Azure Service Bus to SQL Server integration — real-time, two-way sync

Keep Azure Service Bus and SQL Server in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Service Bus and SQL Server

Keep SQL Server and Azure Service Bus in step: the rows in your database and the Queues, Topics, Subscriptions, Messages your engineering tools track stay consistent in real time, in both directions.

SQL Server is where your application's durable data lives; Azure Service Bus is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Tables, Views, Columns, Primary and Unique Keys in SQL Server with Queues, Topics, Subscriptions, Messages in Azure Service Bus field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Feed a cloud warehouse from SQL Server continuously using native CDC instead of SSIS batch jobs
  • 02 Consolidate branch or plant databases into a single operational SQL Server hub
  • 03 Receive messages from a queue or subscription with an AMQP receiver and write them into a Postgres or warehouse table for durable, SQL-queryable storage.
  • 04 Fan out CRM or ERP record changes to a topic and let billing, analytics, and notification subscriptions each filter with SQL rules and react without coupling to the source.

Common sync patterns

Where Azure Service Bus manages users or groups: keep identity aligned

Directory and identity records in Azure Service Bus stay matched to the users or owners table in SQL Server, so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in SQL Server creates or updates the matching record in Azure Service Bus, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

Land tool activity as queryable rows

Records and events from Azure Service Bus arrive in SQL Server as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

What you can sync between Azure Service Bus and SQL Server

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure Service Bus objects SQL Server objects How this pairing syncs
Dead-letter queue A sub-queue on every queue and subscription that automatically holds messages exceeding the max delivery count or their TTL, read for inspection and reprocessing. Views Read-side projections used as outbound sync sources. Dead-letter queue is specific to Azure Service Bus and Views to SQL Server — each maps to any object or custom field on the other side.
Scheduled / deferred messages Messages enqueued for future delivery at a set time, or deferred and set aside by sequence number for retrieval later, out of the normal receive order. Columns Field-level mapping targets with T-SQL types. Scheduled / deferred messages is specific to Azure Service Bus and Columns to SQL Server — each maps to any object or custom field on the other side.
Queues Point-to-point entity: a sender writes messages and one competing consumer at a time receives them under PeekLock, then completes or abandons each message. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Queues is specific to Azure Service Bus and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side.
Topics Publish/subscribe entity a publisher sends to; each message is fanned out to every subscription whose filter rules match, so many consumers get their own copy. CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Topics is specific to Azure Service Bus and CDC Change Tables to SQL Server — each maps to any object or custom field on the other side.
Subscriptions A virtual queue attached to a topic; a consumer receives its own stream of matching messages here, independent of other subscriptions on the same topic. Stored Procedures T-SQL logic that can validate or post-process synced rows. Subscriptions is specific to Azure Service Bus and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Messages The synced unit: a body plus system and user properties, MessageId, SessionId, and TTL; capped at 256 KB on Standard and up to 100 MB on Premium over AMQP. Databases Instance-level databases that scope a sync's reads and writes. Messages is specific to Azure Service Bus and Databases to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Azure Service Bus and SQL Server

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure Service Bus SQL Server Interval-based propagation

DetectionStacksync polls Azure Service Bus for changes on an incremental schedule, reading only records changed since the previous pass. Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or.

DeliveryEach detected change is applied to SQL Server as a row-level write, with types converted between the two schemas.

SQL Server Azure Service Bus Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

DeliveryEach detected change is written to Azure Service Bus through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Azure Service Bus: Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Azure Service Bus ⇄ SQL Server

Connect Azure Service Bus and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Service Bus–SQL Server connection.

Real-time

Two-way sync

Changes in Azure Service Bus or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Service Bus or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure Service Bus or SQL Server record.

Observability

Monitoring

Track your Azure Service Bus ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Service Bus and SQL Server.

How the Azure Service Bus and SQL Server connectors work

Azure Service Bus

Integration surface
AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported)
Authentication
Microsoft Entra ID (Azure AD) RBAC with managed identities - roles Azure Service Bus Data Owner, Data Sender, and Data Receiver - or Shared Access Signature (SAS) policies scoped with Manage, Send, and Listen claims
Change detection
Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or ReceiveAndDelete. No modified-date polling and no native HTTP push; Azure Event Grid can separately raise an 'active messages available' event for intermittent receivers
Capabilities
read · write
Rate limits
Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Azure Service Bus to SQL Server — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure Service Bus and SQL Server with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Service Bus connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Service Bus and SQL Server objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Service Bus ⇄ SQL Server
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Service Bus SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Service Bus and SQL Server integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 418 integrations available for Azure Service Bus and SQL Server.

Popular · 8 of 418
All Azure Service Bus integrations All SQL Server integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own