Introducing SQL projects in SSMS (SSMS 22.5) | Data Exposed
Microsoft Developer introduces SQL projects in SSMS 22.5, showing how to bring an existing production database into source control as a SQL project and use it across VS Code, GitHub Actions, and Azure DevOps for a more reliable database DevOps workflow.
Overview
You have a production database and want to get it into source control and keep it there. In SSMS 22.5, you can import an existing database into a SQL project: a code-based, human-readable definition of your database schema. You can then edit and validate changes without impacting the original database, and publish updates more confidently.
This episode of Data Exposed introduces SQL projects in SSMS and the new Database DevOps workload (preview). It also highlights that the same project file can be used across multiple tools—VS Code, GitHub Actions, and Azure DevOps—so teams can scale their database development process.
What’s new in SSMS 22.5
- Import an existing database into a SQL project
- Work with a human-readable schema definition stored as code
- Edit and validate changes without modifying the source/production database
- Publish changes to apply updates
Tooling and workflow integration
The same SQL project file can be used across:
- SQL Server Management Studio (SSMS)
- Visual Studio Code (VS Code)
- GitHub Actions (automation/CI)
- Azure DevOps (pipelines and team workflows)
Video structure
- 0:00 Introduction
- 2:13 Demos
- 12:00 What’s next
Resources
Social links mentioned
- Anna Hoffman (Twitter): https://twitter.com/AnalyticAnna
- AzureSQL (Twitter): https://aka.ms/azuresqltw
More episodes / channels
- Data Exposed playlist: https://aka.ms/dataexposedyt
- Microsoft Azure SQL channel: https://aka.ms/msazuresqlyt
- Microsoft SQL Server channel: https://aka.ms/mssqlserveryt
- Microsoft Developer channel: https://aka.ms/microsoftdeveloperyt