#sqlpackage
🚀 Faster .dacpac deployments are finally here (preview)!
That reliable ~20 second "startup tax" on every SqlPackage publish is gone — warm publishes now run in ~2 seconds. A 10x win for inner-loop dev and CI. ⚡
How to grab the preview: buff.ly/I62FLbK
#dotnet #SQLServer #DacFx #SqlPackage
From 20+ seconds to 2 - faster SQL Database Project .dacpac deployments are finally here (preview)
If you have ever deployed a SQL Database Project (.sqlproj) or a .dacpac with SqlPackage, you know the drill: you kick off a publish against an empty or near-empty database, grab a coffee, and wait.…
erikej.github.io
August 6, 2026 at 3:41 PM
github.com/microsoft/Da...

Are you a SQL developer? Find out what’s coming in sqlprojects in the 2026 roadmap.
#SQLServer #AzureSQLDB
#DevOps
March 25, 2026 at 9:37 PM
Recently released: Updates to SQL projects in SSMS, VS Code, and SqlPackage - nice to see the continued focus and roadmap updates to keep the DacFX eco system alive and well
#sqlserver #sql #dacfx #vscode
Recently released: Updates to SQL projects in SSMS, VS Code, and SqlPackage | Microsoft Community Hub
Your database should be part of the same development process as the rest of your application, with source control and automation for validation and...
buff.ly
July 21, 2026 at 12:36 PM
There is now a roadmap for sqlpackage / DacFX - note the plans to add support for SQL Database Projects in SSMS!
#dotnet #sqlserver
buff.ly/E8GDDQp
Home
DacFx, SqlPackage, and other SQL development libraries enable declarative database development and database portability across SQL versions and environments. Share feedback here on dacpacs, bacpacs...
github.com
February 11, 2026 at 5:27 PM
[video] SQL DB to MI data mobility with SqlPackage and BACPAC by Rahul Randive: youtu.be/U7qTzwDVHHU
#azuresql #sqlmi #sqldb #bacpac
SQL DB to MI data mobility with SqlPackage and BACPAC
With SqlPackage you can export your Azure SQL Database to a BACPAC file and then import it into Azure SQL Managed Instance. This can be used to effectively c...
youtu.be
September 21, 2023 at 6:15 PM
"Lesson Learned #523: Measuring Import Time -Parsing SqlPackage Logs with PowerShell" buff.ly/mzk4p5i #Microsoft #techcommunity
Lesson Learned #523: Measuring Import Time -Parsing SqlPackage Logs with PowerShell | Microsoft Community Hub
This week I'm working on a service request who was experiencing long import times when restoring a large BACPAC into Azure SQL Database, I need to understand...
buff.ly
June 10, 2025 at 2:32 PM
Any Data folk been able to get sqlpackage installed on a VMSS Azure DevOps Build Agent?

Sysprep removes the installation when generating an image.

Needs to be available for the SqlAzureDacpacDeployment@1 task to use.

#sqlfamily #sqlhelp
February 11, 2025 at 1:29 PM
New release of DacFX and SqlPackage (for automating SQL Database Projects) - adds the ability to ignore post and pre deploy scripts during deployment
#dotnet #dacfx
DacFx and SqlPackage Release Notes - SQL Server
Release notes for Microsoft SqlPackage.
buff.ly
August 1, 2025 at 1:36 PM
"Azure SQL: Optimizing BACPAC Imports - SqlPackage Done Right!" - excellent post on how to make .bacpac imports run fast!
#azuresql #sqlserver #dacfx #sqlpackage
Azure SQL: Optimizing BACPAC Imports - SqlPackage Done Right! | Microsoft Community Hub
This is a frequent scenario, especially when migrating large databases to Azure. The truth is, the time taken for a BACPAC import depends on several factor:...
buff.ly
November 22, 2025 at 8:22 AM
Postgres doesn’t have a sqlpackage tool because Postgres folks are used to working with migrations based deployment approaches. Many of us find it superior and a better approach. People tend to be biased based on what they are used to. 🤷🏻‍♀️
March 24, 2025 at 9:21 PM
Looking for input on improving tooling for going from a database to a SQL project - whether its reducing the number of commands, including the database properties, or another friction point you encounter - github.com/microsoft/Da...
February 19, 2026 at 4:32 PM
Oooh ended up building a sqlpackage GitHub action and docker container as the dependencies for installation were a nightmare.
March 25, 2026 at 9:48 PM
Thanks! 1 and 3 are practically difficult and 2 is a hallucination. Re:1 I found some old SOs but really unsure whether still valid and how it might integrate into sqlpackage
September 3, 2025 at 6:18 PM
If you do a dacpac deployment (which you get after building a database project in VS), sqlpackage will do a schema compare against the target and deploy changes.
April 2, 2025 at 5:29 PM
Database deployments are still one of the trickiest parts of CI/CD. MSBuild.Sdk.SqlProj 4.0 lets you publish SQL database projects as self-contained container images—including the .dacpac and SqlPackage.

Same results. Anywhere containers run.

👉 Read the full post: erikej.github.io/sqlclient/do...
Publish SQL Database Projects as Container Images with MSBuild.Sdk.SqlProj
Database deployments have traditionally been one of the trickier parts of a CI/CD pipeline. You need the right tools installed, the right permissions configured, and the right SQL Server instance reachable—all at deploy time. MSBuild.Sdk.SqlProj simplifies this by letting you manage your SQL Server schema as code and build a .dacpac file just like any other .NET project. Starting with version 4.0.0, it goes one step further by letting you package the .dacpac and the deployment tool into a self-contained container image that can be run anywhere containers can run.
erikej.github.io
April 9, 2026 at 6:31 AM
Curious how #sqlfamily is doing Ci/CD. I’ve checked our DDL into GitHub. How do I get from dev to prod? If I change a table and add a permission, what scripts out the changes from my dev DB? Redgate? Sqlpackage? VS Db Proj? Is there a Best Practice/Guide somewhere? #sqlserver
April 1, 2025 at 6:01 PM