-
Notifications
You must be signed in to change notification settings - Fork 25
Home
The DacFx library and ecosystem encompass a range of functionality for SQL database DevOps, including:
- Deploy, extract, import, export, and schema compare .NET APIs
- SqlPackage CLI
- SQL projects SDK (Microsoft.Build.Sql)
- Tooling surfaces integrations (e.g., VS Code)
- SQL database and Warehouse in Fabric source control and deployment pipelines
- Azure SQL Database import/export
📘 Looking for documentation? Start at aka.ms/sqlprojects or aka.ms/sqlpackage-ref.
Our users include database developers, application developers, DevOps engineers, data engineers and more across a variety of industries and company sizes. The common thread is that they all have a need to manage SQL database schemas and deployments in a more automated and reliable way. We're leaning into empowering teams to adopt DevOps practices for their databases, anchored in a human-readable schema definition (SQL projects) and a dynamic deployment engine. SQL projects work across SQL Server, Azure SQL, and SQL in Fabric, so no matter where your database is based, you can take advantage of these capabilities.
Our primary focus spans three areas:
- Local environments - the tools you're using surface DacFx capabilities that are easy to use and integrate into your workflows
- Continuous integration - database changes are supported with validation and testing for local or automated execution
- Continuous delivery - database changes are readily shared and can be deployed to any target environment with confidence
Whether you're database-first or application-first, there's a workflow that the DacFx ecosystem will improve your confidence that your application deployments will stand the test of time. These tools go beyond deployments to surface capabilities like schema compare, static code analysis, and more to help users understand their databases and improve their development processes.
💬 We love hearing from you! We encourage you to upvote existing feedback and add new feedback so we can prioritize the work that will have the biggest impact for our users. Feedback locations:
- DacFx APIs, SqlPackage, Microsoft.Build.Sql SDK: DacFx GitHub repository
- ScriptDOM parser: ScriptDOM GitHub repository
- SQL Database Projects in VS Code: VS Code repository
- SSMS + Visual Studio: Developer Community
- Fabric integration: Fabric Ideas
The following roadmap is a snapshot of our current plans, but we are always evolving based on user feedback and available resources. We've heard your feedback that you're looking for more transparency into our strategy, and we will do our best to keep this roadmap up to date with our latest plans.
Note
Microsoft.Build.Sql support in Visual Studio 2026 is not yet on the roadmap, but we are actively reviewing the integration. Please continue to voice your feedback on the Developer Community.
- 🧱 Fundamentals (reliability, compatibility, runtime upgrades)
- 🛠️ Tooling foundations (core SQL projects and DacFx capabilities in tools)
- 🧵 Workflow improvement (reducing friction, automation, CI/CD)
Primary milestone: https://github.com/microsoft/DacFx/milestone/15
- 🧱 .NET 10
- 🧱 .NET Standard 2.0
- 🧱 SqlClient 6
- 🧱 Dotnet tool support with .NET 10
- 🛠️ Publish dialog generally available
- 🛠️ Expanded item templates
- 🛠️ Pre-deployment and post-deployment script support
Primary milestone: https://github.com/microsoft/DacFx/milestone/16
- 🧵 SqlPackage config/environment file public preview
- 🧵 Pre-plan script support in Microsoft.Build.Sql preview, GitHub issue
- 🛠️ Code analysis settings
- 🛠️ SQL projects public preview, Developer Community
- 🛠️ Schema compare public preview
- 🧵 Code analysis integration
- 🧵 Rebuilt Azure DevOps task
- 🛠️ Project intellisense
- 🛠️ Object rename/refactoring
- 🧵 Copy database on workspace branch
- 🧱 SQL database in Fabric target platform