Skip to content
Database

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

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

Keep Azure SQL Database and MarkLogic synchronized in real time, across engines, regions, or services, in one or both directions.

Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.

Stacksync syncs tables or collections between Azure SQL Database and MarkLogic continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.

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 curated master data from a MarkLogic data hub into operational CRMs and ERPs.
  • 04 Land document data in relational warehouses by reading TDE views as SQL rows.

Common sync patterns

Regional or environment copies

Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.

Cross-engine sync

Keep the same dataset live in both Azure SQL Database and MarkLogic, so each workload runs on the engine that suits it.

Migration with zero-downtime cutover

When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.

What you can sync between Azure SQL Database and MarkLogic

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 MarkLogic objects How this pairing syncs
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. Document Metadata & Properties Permissions, quality, and property fragments carried with each document. Rows and columns is specific to Azure SQL Database and Document Metadata & Properties to MarkLogic — 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. Databases & Forests Storage units that define the scope and placement of synced content. Stored procedures is specific to Azure SQL Database and Databases & Forests to MarkLogic — 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. Users & Roles Security principals that govern what an integration credential can read or write. Change tracking / CDC tables is specific to Azure SQL Database and Users & Roles to MarkLogic — 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. Documents JSON and XML documents, the primary records read from and written to the database. Tables is specific to Azure SQL Database and Documents to MarkLogic — 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. Collections Named groupings used to scope which documents a sync reads or updates. Views is specific to Azure SQL Database and Collections to MarkLogic — 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. Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. Schemas is specific to Azure SQL Database and Semantic Triples to MarkLogic — each maps to any object or custom field on the other side.

How changes propagate between Azure SQL Database and MarkLogic

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 MarkLogic 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 applied to MarkLogic as a row-level write, with types converted between the two schemas.

MarkLogic Azure SQL Database Interval-based propagation

DetectionStacksync polls MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.

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

What ships with Azure SQL Database ⇄ MarkLogic

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

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

Real-time

Two-way sync

Changes in Azure SQL Database or MarkLogic 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 MarkLogic 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 MarkLogic record.

Observability

Monitoring

Track your Azure SQL Database ⇄ MarkLogic 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 MarkLogic.

How the Azure SQL Database and MarkLogic 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

MarkLogic

Integration surface
REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries
Authentication
Username/password (digest or basic), with certificate-based options
Change detection
No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup
Capabilities
read · write
How it works

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

    Choose tables

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

Azure SQL Database and MarkLogic 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
CSA STAR
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 390 integrations available for Azure SQL Database and MarkLogic.

Popular · 8 of 390
All Azure SQL Database integrations All MarkLogic 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