Microsoft Fabric Connector
QMigrator plays a critical role in this transition by enabling smooth data migration from multiple sources to Microsoft Fabric. Built on a modern, Kubernetes-based architecture, QMigrator ensures high availability, scalability, and flexibility across both on-premises and cloud environments.
Why Fabric?
Organizations are increasingly moving away from legacy on-premises data warehouses, which struggle to meet modern data and analytics demands. Microsoft Fabric offers enhanced scalability, performance, and cost efficiency, making it ideal for today's dynamic business needs. Microsoft Fabric provides a unified data foundation that supports seamless integration, real-time analytics, and end-to-end governance.
Key Highlights
- Multi-Source Database Integration: Supports diverse databases like Oracle, DB2, Postgres, and MSSQL for flexible data ingestion
- Multiple Fabric Targets Support: Enables seamless data movement across Fabric DWH, SQL Server, Lakehouse, and mirrored databases
- Scalable Kubernetes Architecture: Dynamically scales on Kubernetes to manage large workloads, up to 10TB per day
- Autonomous Job Agent: Automates job creation, monitoring, and scaling based on system resource usage
- Real-Time Data Replication: Keeps data continuously synchronized with near real-time access in Fabric environments
- Cost-Efficient Pricing: Usage-based model ensures users pay only for what they use, optimizing cost and ROI
Performance Statistics
| Source | Target | Process | Row Count/Table Count | Data Size(GB) | Time Taken | Throughput |
|---|---|---|---|---|---|---|
| DB2 | Fabric Open Mirroring | Initial Load | 457+ Million/92 | 1024 | 4 hr 9 mins | ~4.11 GB/min |
| Oracle | Fabric Lakehouse | — | — | — | — | — |
| PostgreSQL | Fabric Warehouse | CDC | 20 Million/40 | 27 | 48 mins | 556 MB/min (416,666 transactions/min) |
| SQL Server | Fabric Database | — | — | — | — | — |