Modernizing your application does not have to mean rebuilding it. Many line-of-business applications are tightly connected to their data, making cloud migration feel risky, expensive, and disruptive. But what if the database could move first? This session explores practical patterns for incremental migration without the rewrite or architectural chaos. This is not a "lift and pray" migration, nor a bunch of compromises and workarounds. With stable API layers, modern data access patterns, and new tooling, we will demonstrate how applications can evolve through strategies designed for real systems, real budgets, and real engineering teams.

Connect with .NET: 
Blog:  https://aka.ms/dotnet/blog
Twitter: https://aka.ms/dotnet/twitter
TikTok:  https://aka.ms/dotnet/tiktok
Mastodon:  https://aka.ms/dotnet/mastodon
LinkedIn:  https://aka.ms/dotnet/linkedin
Facebook:  https://aka.ms/dotnet/facebook
Docs: https://learn.microsoft.com/dotnet
Forums: https://aka.ms/dotnet/forums
🙋‍♀️Q&A: https://aka.ms/dotnet-qa
👨‍🎓Microsoft Learn: https://aka.ms/learndotnet

#dotnet

We Are .NET

A step-by-step walkthrough for modernizing a SQL Server-based application without a full rewrite. Covers five incremental stages: migrating from System.Data.SqlClient to Microsoft.Data.SqlClient, upgrading to SQL Server 2025 (with its new vector data type and binary JSON), replacing CRUD APIs with Data API Builder (REST, GraphQL, and MCP endpoints), managing schema via SQL database projects in CI/CD, and enabling AI agents to securely query data through SQL MCP server. Live demos show full-text/BM25 search replaced by vector semantic search, hybrid multi-database routing through a single API surface, and GitHub Copilot using the MCP endpoint to query products.

Cloud-Native Data Without Starting Over