In today’s multi-cloud landscape, flexibility and data portability are increasingly important considerations. While public cloud database services offer convenience, some organizations may reassess public-cloud database deployments based on data-transfer charges, scaling requirements, portability, and operating-model considerations.
To regain control over their data, optimize total cost of ownership (TCO), and achieve consistent performance, some organizations evaluate private or hybrid-cloud environments for selected workloads.
When it comes to database infrastructure, NDB provides a Database-as-a-Service (DBaaS) operating model for database lifecycle management across supported environments.
If you are currently planning to migrate an Azure SQL database back to an SQL Server instance deployed and managed through NDB, this guide provides a comprehensive architectural roadmap and execution framework to complete the journey with a short planned outage, subject to validation.
NDB simplifies database lifecycle management across hybrid environments. Key advantages include:
Before diving into configuration, it is critical to select the right tool for your specific database architecture. Depending on your table structures, data volume, and network constraints, you will typically leverage either Azure SQL Data Sync or Azure Data Factory (ADF).
| Evaluation Metric | Method 1: Azure SQL Data Sync | Method 2: Azure Data Factory (ADF) |
|---|---|---|
| Ideal For | Small-to-medium OLTP databases. | ADF may be appropriate for large or complex migrations requiring pipeline orchestration, subject to throughput and supportability validation. |
| Primary Key Requirement | Strictly Mandatory for all synchronized tables (confirm from Microsoft documentation) | Not Mandatory (Flexible schema support, Primary keys are not inherently required for a basic copy, but the incremental design still requires a reliable change-detection and reconciliation strategy). |
| Synchronization Logic | Continuous, one-way cloud-to-local replication group. | Incremental "delta" copies triggered by watermark columns. |
| Setup Complexity | Lower (Relies on a lightweight local agent). | Higher (Requires pipelines, links, and integration runtimes). |
| Scale Limitations | Best suited for moderate data volumes and standard data types. | Engineered for high-volume, enterprise-grade data movement. |
| Downtime | Based on the synch frequency | Based on the ADF synch interval |
To help prepare for a controlled data transfer, ensure the following foundational prerequisites are met before initiating either migration method:
Azure SQL Data Sync is ideal for databases where all tables have Primary Keys. It allows for one-way synchronization from the cloud "Hub" to the NDB "Member."
Figure 1: Architecture of the Sync Group showing the Hub (Azure SQL) and Member (NDB SQL VM) relationship.
Figure 2: Defining the central Sync Group parameters, hub credentials, and the desired refresh frequency within the Azure Portal.
Figure 3: Registering the target NDB environment inside the on-premises Data Sync Agent utility.
Figure 4: Finalizing member rules, setting traffic direction to pull from the cloud, and mapping schema tables.
While Data Sync is highly effective, enterprise environments must account for several technical guardrails:
For massive, enterprise-scale data volumes or complex schemas that lack uniform primary keys, Azure Data Factory (ADF) offers a robust pipeline-driven approach. ADF can use a watermark or another documented change-detection strategy; the design must explicitly address inserts, updates, deletes, retries, and watermark persistence and sequentially sync delta records down to NDB provisioned on-prem databases.
Figure 5: Enterprise data plumbing showcasing the network communication path between Azure Data Factory and the NDB target environment via a Self-hosted Integration Runtime.
Figure 6: Verifying the operational status of the on-premises Self-hosted Integration Runtime within the ADF dashboard.
Figure 7: Mapping connection endpoints for both the source cloud repository and the destination database engine.
Figure 8: Real-time monitoring of the iterative pipeline execution, validating data movement and watermark precision.
Migrating at scale via ADF requires strict adherence to schema best practices:
Once your data is successfully replicating and your delta gap is closed, it is time to execute your final production cutover window. Follow these steps to support data-integrity validation:
Pause all inbound application transactions routing to the live Azure SQL database. This freezes the source state and prevents mid-cutover data discrepancies.
Trigger a final manual sync iteration via Data Sync or your ADF pipeline.The final synchronization duration depends on remaining change volume, transaction rate, network capacity, synchronization latency, and pipeline performance. Measure it during a rehearsal to understand the entirety of your application's actual data-downtime window.
Before opening up connection routes to the new NDB instance, execute these verification commands on the target SQL engine:
Update your core application connection strings to target your SQL Server instance managed through NDB. Restore user traffic, check performance baselines, and re-enable your NDB Time Machine protection rules to begin automated snapshots.
Migrating your primary databases off public cloud instances doesn't have to imply massive disruption or daunting project timelines. Whether you opt for the continuous, straightforward synchronization of Azure SQL Data Sync or the enterprise-scale orchestration capabilities of Azure Data Factory, Nutanix Database Service (NDB) serves as a robust target platform for enterprise SQL workloads.
Migrating to NDB can provide greater control over the target deployment and operating model, deliver infrastructure and operational cost predictability, and reduce dependence on a single public-cloud database service, all while retaining a DBaaS-oriented operating model for supported database operations.
©2026 Nutanix, Inc. All rights reserved. Nutanix, the Nutanix logo and all Nutanix product and service names mentioned are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. All other brand names mentioned are for identification purposes only and may be the trademarks of their respective holder(s).