Migrating from SQL to NoSQL with .NET and Dapper
summary
A .NET utility (github.com/mgroves/SqlServerToCouchbase) reads AdventureWorks via Dapper buffered=false streaming, creates Couchbase artifacts (creates buckets scopes collections), serializes rows to JSON and writes with upsert per document, copies some indexes (demo copies ~5 of 100+), and attempts to map users and queries. It handles SQLServer types like geography, skips temporal/history tables and sprocs, and reports similar sanity-check latency (~70 ms under 250 clients) while noting manual work for constraints and complex logic.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:56SQL-to-Couchbase dictionary
- 11:35Step 0: Connect to database
- 14:03Step 1: Create bucket
- 17:11Step 2: Scopes and collections
- 21:38Step 3: Copy data
- 27:43Step 4: Copy indexes
- 31:29Step 5: Copy users
- 33:07Step 6: Application
- 38:58Demo
- 52:30What can't be automated yet
- 56:00Should I automate this process?
- 1:01:56What's next?
- 1:03:10Q&A
related talks
54mBetter Object Mapping in .NET with Dapper
54mSay Yes to NoSQL for the .NET SQL Developer
01h 01mFrom SQL to Azure Cosmos DB
01h 02mZero to Document Hero
01h 02mFrom SQL to Azure Cosmos DB
35mA Customer’s Journey: Migrating from NoSQL to a Cloud Native Distributed SQL Database
45mDemystifying NoSQL: The SQL developer's guide
14mUse EF Core to transition from SQL Server to Azure Cosmos DB
