SQL Server vs Azure Cosmos DB
summary
Compares Azure SQL and Cosmos DB with concrete tradeoffs: Cosmos DB physical partitions cap at 50 GB per physical partition and add partitions when traffic hits 10,000 RU/s, point reads can cost as little as 1 RU while cross-partition queries multiply RU cost; demo VS Code extension shows partition hashes, execution metrics and an indexing matrix and proves a query hitting five partitions costs 450 RUs but returns 10 visible items; pricing examples include 400 RU minimum (~$25–30/mo) and serverless 1M RUs for $0.28.
AI-written summary · about
chapters (15)
- 0:00SQL Server vs Cosmos DB
- 4:25PARTITIONING IN SQL SERVER
- 7:35COSMOS DB LOGICAL PARTITION
- 9:55QUERY PLAN ENGINE
- 13:45AVAILABLE DATA MODELS
- 15:33INDEXES
- 18:43CONNECTIONS
- 21:21SPROCS
- 22:54TRIGGERS
- 23:53PRICING
- 27:11CHANGE FEED
- 31:22PERFORMANCE TUNING
- 33:41NULL & UNDEFINED
- 35:15DATA MODELLING
- 40:06WHICH ONE SHOULD I USE?
related talks
55mSQL Server vs Azure Cosmos DB
16mAzure Cosmos DB: A look at the Universe
01h 00mCost cutting strategies for Azure Cosmos DB
08mOptimize for the Best Cost and Performance for Azure Cosmos DB NoSQL API
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
46mDesign and build multi-tenant SaaS apps at scale with Azure Cosmos DB
52mPerformance tuning for Azure Cosmos DB
01h 03mData Modeling and Partitioning in Azure Cosmos DB