Blog Post

Azure SQL Blog
3 MIN READ

Database DevOps (preview) in SSMS 22.4.1

DrewSkwiersKoballa's avatar
Mar 19, 2026

Database DevOps tooling for Microsoft SQL brings the benefits of database-as-code to your development workflow. At its core are SQL database projects, which enable you to source control your database schema, perform reliable deployments to any environment, and integrate code quality checks into your development process. Whether you're managing a single database or orchestrating complex deployments across multiple environments, SQL projects in SQL Server Management Studio (SSMS) provide the foundation for modern database DevOps practices.

Introducing SQL projects in SSMS

With the 22.4 release of SQL Server Management Studio (SSMS), we are excited to launch the public preview of SQL projects with the new "Database DevOps" workload in SSMS. This marks a significant milestone in our journey to bring the power of SQL projects to database professionals in different roles and with different preferences for development environments. The initial public preview brings the core create, build, and publish workflow to SSMS with the backing of Microsoft.Build.Sql projects, which are also supported in VS Code. This means that you can create a SQL project in SSMS, check it into source control, and then work with it in VS Code or vice versa, enabling a seamless experience across different tools and teams.

This is just the beginning of our plans for SQL projects in SSMS, and we are committed to expanding the capabilities and integrations in future releases based on your feedback and needs. Additional functionality in upcoming releases includes creating and updating projects from databases directly as well as the graphical schema compare interface. If you're looking to bring an existing database into source control and start with SQL projects in SSMS today, you have two options for quickly accessing your database definition. The mssql extension in VS Code provides a menu item in object explorer for "Create project from database" and the SqlPackage CLI has a command to generate the .sql files that can be copied directly into the SQL project directory:

dotnet tool install -g microsoft.sqlpackage sqlpackage /action:extract /sourceconnectionstring:"<connection string>" /targetfile:"databasefiles" /p:extracttarget=schemaobjecttype

What about Visual Studio SQL Server Data Tools (SSDT)?

SQL projects in SSMS are based on Microsoft.Build.Sql projects and requires a minimum SDK version of 2.1.0. While a preview of SSDT for Microsoft.Build.Sql projects is available for Visual Studio 2022, only the original SQL projects are supported in SSDT for Visual Studio 2026. The SQL projects tooling ecosystem includes multiple development environments, CI/CD integrations, and even customization through the DacFx .NET library. Our goal is that this ecosystem enables you and your teams to manage SQL database schemas and deployments in a more automated and reliable way, and this requires that tools used by your teams surface SQL projects such that they can be integrated into your existing workflows.

I understand that initial messaging about Microsoft.Build.Sql projects for Visual Studio and changes when that work was delayed has led to some confusion, so we’re operating with as much transparency as we can with the SQL projects roadmap at aka.ms/sqlprojects-roadmap. You'll note at this time that Microsoft.Build.Sql support in Visual Studio 2026 is not yet on the roadmap. Please continue to voice your feedback on the Developer Community, which is extremely valuable as we are actively reviewing the integration.

Get to know SQL projects

SQL projects represent a fundamental file format for database development and automation, enabling both a declarative approach to defining and deploying database schemas as well as supporting migration-based deployment methods with consolidated change visibility and code quality checks. By adopting SQL projects, teams can achieve greater consistency, collaboration, and efficiency in their database development processes, ultimately leading to more reliable and maintainable database systems. The integration of SQL projects with modern development tools and platforms further enhances their value, making it easier for teams to implement DevOps practices and automate their database workflows.

Documentation is available at aka.ms/sqlprojects-docs, and our public roadmap at aka.ms/sqlprojects-roadmap shows what's coming next. We'd love to hear your feedback — your input directly shapes our priorities and helps us build the database DevOps experience that works best for your teams. Get started with the public preview of SQL projects in SSMS today by downloading SSMS 22 or updating your current SSMS to 22.4 and modifying the SSMS install to include the Database DevOps workload.

Published Mar 19, 2026
Version 1.0

6 Comments

  • Rallets's avatar
    Rallets
    Copper Contributor

    Be aware that SDK-style database projects are NOT supported from Visual Studio 2026 and any plans to support it have been cancelled by Microsoft itself. So chose very carefullly what database-project style you want to pick for your project.
    Ref: https://developercommunity.visualstudio.com/t/Visual-Studio-2026-still-using-old-SQL-S/10965461

    • DrewSkwiersKoballa's avatar
      DrewSkwiersKoballa
      Icon for Microsoft rankMicrosoft

      That's a bit of an over simplification. There were efforts to bring the modern SQL projects to Visual Studio 2022 and conflicting changes landing in Visual Studio 2026 forced that work to be paused. The feedback item you've linked shows that the work is under review (https://developercommunity.visualstudio.com/t/Visual-Studio-2026-still-using-old-SQL-S/10965461) and every developer that votes, reaches out to their account team, etc. is a vital part of how we prioritize our roadmap.

  • jancg's avatar
    jancg
    Copper Contributor

    How do these new features fit alongside EF Code First Migrations?

    • Great question! Deciding how to fit any ORM (including EF Core) in with database development and CI/CD practices depends on a couple of factors, including:

      • do developers need or want to review the database changes proposed by the ORM for quality or correctness? One approach can be to automate the generation of a SQL project from a database generated by EF Core in a CI pipeline (sqlpackage /a:extract /p:ExtractTarget=sqlproject), which would give you source controlled visibility to the actual T-SQL objects and the ability to apply sql code analysis before antipatterns make it downstream.
      • how mature/old is the application? A long history of migrations may be causing slower deployments or difficulty in pinpointing what will actually run at this point, and compressing/consolidating them can be challenging for some teams. Getting a single customized deployment script per environment can be worth the time to setup either reverse engineering to a SQL project or extracting a dacpac from a staging environment.
      • is the application deployed to 1, 5, 100, or more environments? The more complex/sophisticated the infrastructure requirements, the more meaningful being able to deploy just-in-time changes and checking for environment drift become.
      • do database-focused developers or DBAs apply object changes or fixes further in the app dev lifecycle? For example - adding/modifying indexes or changing stored procedures. SQL projects provide a way to create a single source of truth for the database environment that multiple people/teams can share.

       

      This presentation from 2025 focused on the ways SQL projects can support development, including development using EF Core: https://www.youtube.com/watch?v=4P1cSyKiYVw

  • SaverioParlato's avatar
    SaverioParlato
    Copper Contributor

    First issue found - Management Studio 22.4.1, Database DevOps (Preview) added (and laptop restart performed); trying to create a new SQL Database project in SSMS using default path (C:\Users\myuser\Source\Repos) and I get this error: "The SDK 'Microsoft.Build.Sql/2.1.0' specified could not be found. C:\Users\myuser\Source\Repos\myTestProject\myTestProject.sqlproj". The .NET 10 SDK is successfully installed on the laptop, so I don't understand why I'm getting this error

     

    • DrewSkwiersKoballa's avatar
      DrewSkwiersKoballa
      Icon for Microsoft rankMicrosoft

      SaverioParlato​ - blog post comments probably aren't the best way to get support. When you run into trouble with SSMS you can click the feedback button in the upper right corner. There's also the link aka.ms/ssms-feedback that redirects there as well.