--- title: Migrate to Azure SQL. Then Build Something New | daily.dev description: A Microsoft principal PM demonstrates migrating a live app from SQL Server 2025 to Azure SQL Database Hyperscale using new AI-powered skills and tools. The... canonical: https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Migrate to Azure SQL. Then Build Something New | daily.dev og:description: A Microsoft principal PM demonstrates migrating a live app from SQL Server 2025 to Azure SQL Database Hyperscale using new AI-powered skills and tools. The... og:url: https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue og:image: https://api.daily.dev/og/posts/alY0f0Tue.png og:image:alt: Migrate to Azure SQL. Then Build Something New og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Migrate to Azure SQL. Then Build Something New **[Microsoft Developer](https://daily.dev/sources/microsoftdeveloper)** · 22 min read · 0 upvotes · 0 comments ## Summary A Microsoft principal PM demonstrates migrating a live app from SQL Server 2025 to Azure SQL Database Hyperscale using new AI-powered skills and tools. The demo covers both a DBA workflow in SQL Server Management Studio and a developer workflow in VS Code using Copilot and preloaded migration skills. The assessment flags Service Broker as a migration blocker, which Copilot disables after confirming the app does not use it. A backpack export and import completes the migration in about 7 minutes 32 seconds, after which Copilot switches the app's connection to Azure SQL DB Hyperscale and applies security best practices like disabling trust server certificate. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What causes a migration blocker when moving a SQL Server database to Azure SQL Database? Service Broker being enabled on the database is a common blocker for migrating to Azure SQL Database. If no queues, services, routes, or contracts are defined, it is likely unused and can be safely disabled, after which the application should be verified to continue working before re-running the migration assessment. _Teams planning a SQL Server to Azure SQL cutover can track migration tooling updates like this on daily.dev._ ### Why does Azure SQL Hyperscale get recommended over other Azure SQL tiers during migration assessments? Azure SQL Database Hyperscale is recommended because it does not charge for SQL licensing fees under certain models and supports databases up to 128TB, among other benefits. A migration assessment tool gave a specific recommendation of about 6 vCores and 10GB of storage for one sample workload, with pricing differences shown for savings or reserved plans. _Developers weighing Azure SQL tiers for a migration can follow coverage like this on daily.dev._ ### How long does a backpack export and import take when migrating a database to Azure SQL? One live migration of a session-scheduling database from SQL Server 2025 to Azure SQL Database Hyperscale took about 7 minutes and 32 seconds for the full backpack export and import process. After completion, a post-migration verification step compared row counts between source and target but did not validate row content or whether the app was frozen during export. _Anyone estimating downtime for a database cutover can keep tabs on migration benchmarks via daily.dev._ ## Similar posts on daily.dev - [How to build an app on Azure SQL with an AI coding agent](https://daily.dev/posts/how-to-build-an-app-on-azure-sql-with-an-ai-coding-agent-hyseem3y2) · DevBlogs · 0 upvotes · 0 comments --- Tags: [#database](https://daily.dev/tags/database), [#azure](https://daily.dev/tags/azure), [#mcp](https://daily.dev/tags/mcp), [#vscode](https://daily.dev/tags/vscode), [#microsoft-sql-server](https://daily.dev/tags/microsoft-sql-server) [View this post on daily.dev](https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Migrate to Azure SQL. Then Build Something New","url":"https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue"},"datePublished":"2026-10-20T21:25:09.443Z","dateModified":"2026-10-20T21:25:35.554Z","description":"A Microsoft principal PM demonstrates migrating a live app from SQL Server 2025 to Azure SQL Database Hyperscale using new AI-powered skills and tools. The...","image":"https://i.ytimg.com/vi/yOxoJwaFFsI/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/yOxoJwaFFsI/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Microsoft Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Microsoft Developer","logo":"https://media.daily.dev/image/upload/s--xZzU3zUq--/f_auto/v1746714872/logos/microsoftdeveloper","url":"https://daily.dev/sources/microsoftdeveloper"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"database,azure,mcp,vscode,microsoft-sql-server","timeRequired":"PT22M","video":{"@type":"VideoObject","name":"Migrate to Azure SQL. Then Build Something New","description":"A Microsoft principal PM demonstrates migrating a live app from SQL Server 2025 to Azure SQL Database Hyperscale using new AI-powered skills and tools. The...","thumbnailUrl":"https://i.ytimg.com/vi/yOxoJwaFFsI/sddefault.jpg","uploadDate":"2026-10-20T21:25:09.443Z","duration":"PT22M","url":"https://api.daily.dev/r/alY0f0Tue","embedUrl":"https://www.youtube.com/embed/yOxoJwaFFsI"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Microsoft Developer","item":"https://daily.dev/sources/microsoftdeveloper"},{"@type":"ListItem","position":3,"name":"Migrate to Azure SQL. Then Build Something New"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/migrate-to-azure-sql-then-build-something-new-aly0f0tue#faq","mainEntity":[{"@type":"Question","name":"What causes a migration blocker when moving a SQL Server database to Azure SQL Database?","acceptedAnswer":{"@type":"Answer","text":"Service Broker being enabled on the database is a common blocker for migrating to Azure SQL Database. If no queues, services, routes, or contracts are defined, it is likely unused and can be safely disabled, after which the application should be verified to continue working before re-running the migration assessment. Teams planning a SQL Server to Azure SQL cutover can track migration tooling updates like this on daily.dev."}},{"@type":"Question","name":"Why does Azure SQL Hyperscale get recommended over other Azure SQL tiers during migration assessments?","acceptedAnswer":{"@type":"Answer","text":"Azure SQL Database Hyperscale is recommended because it does not charge for SQL licensing fees under certain models and supports databases up to 128TB, among other benefits. A migration assessment tool gave a specific recommendation of about 6 vCores and 10GB of storage for one sample workload, with pricing differences shown for savings or reserved plans. Developers weighing Azure SQL tiers for a migration can follow coverage like this on daily.dev."}},{"@type":"Question","name":"How long does a backpack export and import take when migrating a database to Azure SQL?","acceptedAnswer":{"@type":"Answer","text":"One live migration of a session-scheduling database from SQL Server 2025 to Azure SQL Database Hyperscale took about 7 minutes and 32 seconds for the full backpack export and import process. After completion, a post-migration verification step compared row counts between source and target but did not validate row content or whether the app was frozen during export. Anyone estimating downtime for a database cutover can keep tabs on migration benchmarks via daily.dev."}}]} ```