Skip to content

Databases

Managed operational databases on Azure: the Azure SQL family (SQL Database, SQL Managed Instance, SQL Server on Azure VMs), Azure Cosmos DB for NoSQL and vector workloads, Azure DocumentDB for MongoDB compatibility, and Azure Database for PostgreSQL flexible server.

3 technology profiles in this area

Overview

Azure SQL is a family, not one service. Azure SQL Database is PaaS for cloud applications with serverless and Hyperscale options. Azure SQL Managed Instance offers near-complete SQL Server engine compatibility, and Microsoft describes it as the fit for most migrations. SQL Server on Azure VMs gives full control of the operating system and engine. A SQL database in Microsoft Fabric is a separate product that mirrors automatically to OneLake.

Azure Cosmos DB is a managed NoSQL and vector database with multi-region writes and a 99.999% availability SLA for multi-region setups. Azure DocumentDB, built on PostgreSQL with MongoDB wire compatibility, suits teams that need deep MongoDB fidelity. Azure Database for PostgreSQL flexible server runs community PostgreSQL with optional zone-redundant high availability.

Microsoft itself says Cosmos DB is a poor fit for analytical (OLAP) and highly relational workloads and suggests Fabric or Azure SQL for those. For small or development workloads, Azure SQL Database has a Basic tier and PostgreSQL flexible server has a Burstable tier.123

Problems it addresses

  • Migrating SQL Server without rewrites1

    SQL Managed Instance supports migration with minimal to no database changes, and SQL Server on Azure VMs keeps full compatibility with operating system access.

  • Global, low-latency apps2

    Cosmos DB offers turnkey multi-region writes with automatic failover and single-digit millisecond response times.

  • Storing vectors next to data2

    Cosmos DB includes vector and hybrid search (DiskANN), so embeddings can sit beside operational data for retrieval and agents.

  • MongoDB workloads2

    Azure DocumentDB keeps MongoDB-compatible drivers and tools, while Microsoft suggests the Cosmos DB API for NoSQL for most new global apps.

  • Analytics on operational data2

    Mirroring into Fabric gives near real-time analysis without building ETL jobs.

A typical workflow

  1. Classify workloads1

    Sort applications by data shape (relational, document, key-value, vector) and note which depend on operating system access.

  2. Pick the SQL option1

    Use the Azure SQL hub's recommendation wizard to compare SQL Database, Managed Instance and SQL Server on VMs.

  3. Choose NoSQL or PostgreSQL2

    Use Cosmos DB for scale-out and global distribution, DocumentDB for MongoDB fidelity, or PostgreSQL flexible server for community Postgres.

  4. Migrate3

    Use Azure Database Migration Service for PostgreSQL moves with minimal downtime, or dump and restore when downtime is acceptable.

  5. Connect to analytics4

    Mirror operational data into Fabric OneLake for reporting without ETL.

Technologies

  • Cloud service

    Azure Cosmos DB

    Azure Cosmos DB is a fully managed NoSQL and vector database for applications that need low latency, elastic scale and global distribution. It offers multi-region writes with a 99.999% availability SLA, built-in vector and hybrid search, and serverless or provisioned throughput billed in request units.

    • Data
    • AI
  • Cloud service

    Azure Database for PostgreSQL

    Azure Database for PostgreSQL is a fully managed service that runs community PostgreSQL on Azure, with zone-redundant HA, automated patching and backups, elastic clusters for sharding, and AI extensions such as pgvector, DiskANN and azure_ai. Azure HorizonDB is a separate PostgreSQL-based service in preview.

    • Data
    • AI
  • Cloud service

    Azure SQL

    Azure SQL is Microsoft's family of SQL Server engine services on Azure: Azure SQL Database for cloud applications (with Hyperscale and serverless options), Azure SQL Managed Instance for near-complete SQL Server compatibility, and SQL Server on Azure Virtual Machines for full OS and engine control.

    • Data
    • AI

Use cases

Documented implementations

Next steps

  1. Inventory SQL Server instances and flag those with SQL Agent or operating system dependencies.

  2. Try the Cosmos DB free tier or local emulator before committing to a data model.

  3. Apply Azure Hybrid Benefit if you already own SQL Server licenses.

  4. Decide which operational tables should be mirrored into Fabric for reporting.

Sources

  1. What is Azure SQL? (opens in a new tab)Microsoft · Vendor-reported
  2. Azure Cosmos DB overview (Unified AI Database) (opens in a new tab)Microsoft · Vendor-reported
  3. What is Azure Database for PostgreSQL flexible server? (opens in a new tab)Microsoft · Vendor-reported
  4. What is Microsoft Fabric (opens in a new tab)Microsoft · Vendor-reported

Fill out the form below to request your copy.

Name(Required)