Skip to content
Database ⇄ Developer tools

Azure SQL Database to Newrelic integration — real-time, two-way sync

Keep Azure SQL Database and Newrelic 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 SQL Database and Newrelic

Keep Azure SQL Database and Newrelic in step: the rows in your database and the Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions your engineering tools track stay consistent in real time, in both directions.

Azure SQL Database is where your application's durable data lives; Newrelic 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 Change tracking / CDC tables, Tables, Views, Schemas in Azure SQL Database with Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions in Newrelic 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 an Azure SQL operational database with orders and inventory from an ERP in near real time.
  • 02 Expose SaaS data (billing, support tickets) as tables in Azure SQL for reporting teams already on Microsoft tooling.
  • 03 Sync the Entity catalog into a CMDB or warehouse for asset inventory, and add or replace entity Tags to keep ownership and environment metadata current.
  • 04 Provision Synthetics Monitors from a service catalog and read their results via NRQL for availability and latency reporting in SQL.

Common sync patterns

One integration pattern instead of per-tool API code

Read and write the synced tables in Azure SQL Database and Stacksync keeps Newrelic current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

React to changes on either side in near real time

Updates in Newrelic arrive as row changes in Azure SQL Database, and writes to Azure SQL Database propagate to Newrelic within seconds, so triggers, jobs, and alerts fire without polling.

Where Newrelic manages users or groups: keep identity aligned

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

What you can sync between Azure SQL Database and Newrelic

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 SQL Database objects Newrelic objects How this pairing syncs
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. Alert Policies & Conditions Alert policies and NRQL alert conditions managed through NerdGraph alertsPolicy and alertsNrqlCondition mutations with full create, update, and delete; read out for audit or provisioned from a config source so alerting stays consistent across accounts. Rows and columns is specific to Azure SQL Database and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side.
Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. NRQL Query Results Telemetry events, metrics, logs, and spans queried through NerdGraph's nrql field (or the legacy Insights query API) over time windows; read-only and bounded by data retention, commonly streamed into a warehouse for long-term analysis. Stored procedures is specific to Azure SQL Database and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side.
Change tracking / CDC tables System-maintained change records used to drive incremental sync. Entities The entity catalog of APM applications, hosts, services, and monitors searched via NerdGraph entitySearch; read for inventory, with tags added or replaced through taggingAddTagsToEntity so ownership and environment metadata stay in sync. Change tracking / CDC tables is specific to Azure SQL Database and Entities to Newrelic — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map one-to-one to records in the paired system. Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. Tables is specific to Azure SQL Database and Workloads to Newrelic — each maps to any object or custom field on the other side.
Views Read-only projections used when the sync should expose a curated shape rather than raw tables. Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. Views is specific to Azure SQL Database and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side.
Schemas Namespaces that organize tables and control which objects a sync user can reach. Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. Schemas is specific to Azure SQL Database and Custom Events to Newrelic — each maps to any object or custom field on the other side.

How changes propagate between Azure SQL Database and Newrelic

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 SQL Database Newrelic Sub-second propagation

DetectionChanges in Azure SQL Database are captured at the source via change data capture — no polling loop against its API. Change data capture or change tracking, both supported on Azure SQL Database.

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

Newrelic Azure SQL Database Sub-second propagation

DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).

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

Rate-limit considerations

  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
What ships with Azure SQL Database ⇄ Newrelic

Connect Azure SQL Database and Newrelic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure SQL Database–Newrelic connection.

Real-time

Two-way sync

Changes in Azure SQL Database or Newrelic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure SQL Database or Newrelic 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 SQL Database or Newrelic record.

Observability

Monitoring

Track your Azure SQL Database ⇄ Newrelic sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Newrelic.

How the Azure SQL Database and Newrelic connectors work

Azure SQL Database

Integration surface
SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
Authentication
SQL authentication (database credentials) or Microsoft Entra ID authentication
Change detection
Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback
Capabilities
read · write · CDC

Newrelic

Integration surface
NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
Authentication
User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
Change detection
NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
How it works

How to connect Azure SQL Database to Newrelic — 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 SQL Database and Newrelic 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 SQL Database connected
    Newrelic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure SQL Database and Newrelic 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 SQL Database ⇄ Newrelic
    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 SQL Database Newrelic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure SQL Database and Newrelic 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 322 integrations available for Azure SQL Database and Newrelic.

Popular · 6 of 322
All Azure SQL Database integrations All Newrelic 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