SQL Server vs Azure Cosmos DB
summary
SQL Server is a mature relational engine (about 30 years) that supports JSON/XML, rich indexing and cached T-SQL plans; Cosmos DB is cloud-native (about 7 years) with partitioning and pricing that force different design choices. Cosmos requires choosing a partition key to avoid cross-partition queries (logical partition limit 20 GB per key) and scales by physical partitions of 50 GB and 10,000 request units each; a point read costs 1 RU, cross-partition queries can cost dozens of RUs but are fixed by change feed + Azure Functions materialized views. VS Code Cosmos DB SQL Studio exists and is demoed.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:39Architectural overview
- 6:51Partitioning strategies
- 10:07Partition key mechanisms
- 12:35Query plan and execution
- 17:10Data model flexibility
- 18:41Indexing and performance
- 21:52Stored procedures and logic
- 23:43Triggers and automation
- 24:42Computed columns and properties
- 26:13Pricing and cost management
- 29:05Views and materialized views
- 33:24Performance tuning
- 37:29Handling null values
- 39:12Data modeling best practices
- 41:39Selecting the right tool
- 46:01Getting started and demo
related talks
49mSQL Server vs Azure Cosmos DB
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
16mAzure Cosmos DB: A look at the Universe
54mSay Yes to NoSQL for the .NET SQL Developer
19mRelational or Non-Relational? Choosing the Best Database for the Task
01h 03mAzure Cosmos DB - The Best NoSQL Database You're Probably Not Using (Yet)
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right