You have a database in production. How do you get it into source control — and keep it there? With SSMS 22.5, you can now import your database into a SQL project — a code-based, human-readable definition of your schema — edit and validate without impacting the original database, and publish changes with confidence. In this Data Exposed episode, we introduce SQL projects in SSMS with the new Database DevOps workload in preview. We'll also show how the same project file works across VS Code, GitHub Actions, and Azure DevOps — so your database development process can grow with your team across any tool.

✅ Chapters:
0:00 Introduction
2:13 Demos
12:00 What's next

✅ Resources:
https://aka.ms/sqlprojects
https://aka.ms/ssms-sqlprojects

📌 Let's connect:
Twitter - Anna Hoffman, https://twitter.com/AnalyticAnna
Twitter - AzureSQL, https://aka.ms/azuresqltw
 
🔴 Watch even more Data Exposed episodes: https://aka.ms/dataexposedyt
 
🔔 Subscribe to our channels for even more SQL tips:
Microsoft Azure SQL: https://aka.ms/msazuresqlyt
Microsoft SQL Server: https://aka.ms/mssqlserveryt
Microsoft Developer:  https://aka.ms/microsoftdeveloperyt
 
#AzureSQL #SQL #LearnSQL

Microsoft Developer

SQL Projects are now available in preview in SQL Server Management Studio (SSMS). The feature enables database-as-code workflows, allowing developers and DBAs to manage database schemas in source control. Key capabilities include importing an existing database into a SQL project, targeting multiple SQL platforms (SQL Server and Azure SQL Database), and integrating with CI/CD pipelines via GitHub Actions using the sqlpackage CLI. The tool handles schema migrations automatically, removing the need to manually write ALTER TABLE migration scripts. Schema compare and database references are planned for a future release this quarter.

Introducing SQL projects in SSMS | Data Exposed