Cloud-Native Data Without Starting Over
summary
Stepwise modernization shows concrete swaps and results: replace system.data.sqlclient with Microsoft.Data.SqlClient as a drop‑in, run SQL Server locally in containers and upgrade to SQL Server 2025 to gain a vector data type (semantic search distances like 0.4 and 0.75) and binary JSON, track schema with SQL database projects, and remove Entity Framework by routing queries through Data API Builder so the same CRUD and stored‑procedure results return (top 10 ranks) while SQL MCP server exposes a secure JSON‑RPC agent endpoint that successfully executes queries.
AI-written summary · about
chapters (9)
- 0:00Modernizing database layer
- 2:36Updating SQL drivers
- 5:07Upgrading to SQL Server 2025
- 7:22Data API builder implementation
- 9:14SQL database projects
- 10:20Hybrid cloud and scaling
- 12:19Enabling AI agents
- 13:19Hands-on demonstration
- 28:50Summary and conclusions
related talks
01h 02mNot your Father's SQL Server: Developer Innovations in Data Storage
32mCloud-Native Data: What is it? - Majors, Dunlap, O’Grady, Richardson, Drewitz
43mIncrease developer velocity with Azure SQL Database from data to API
54mSay Yes to NoSQL for the .NET SQL Developer
56mDeveloping AI Applications with SQL AI: Ground to Cloud to Fabric
52mData storage for modern applications - Mike Lehan
51mDatabase systems: a decade of disruption and innovation
01h 00m20 year old cloud native apps with .NET