Publishing SQL database projects shouldn’t be the hardest part of CI/CD.
With MSBuild.Sdk.SqlProj 4.0, you can now publish your .dacpac and SqlPackage as a runnable container image.
Reproducible. Portable. No agents to configure.
👉 Read more: erikej.github.io/sqlclient/d…#dotnet#sqlserver#containers#devops#cicd
Import or export Azure SQL Databases securely—no public Azure access needed! 🔐 Run import/export operations even when “Allow Azure services and resources to access this server” is turned OFF by using a locked-down Azure VM with SqlPackage.
⚡ Perform imports/exports via BACPAC files
🛡️ Keep network access tightly controlled with firewall rules
🛠️ Optimize performance with the right VM size, region, and storage
Learn how 👉 msft.it/6014Qi8oI#AzureSQL#Security#Database#Cloud
ALT Screenshot of Azure portal, connect to VM, with download RDP highlighted.
New release of DacFX and SqlPackage (for automating SQL Database Projects) - adds the ability to ignore post and pre deploy scripts during deployment
#dotnet#dacfxlearn.microsoft.com/en-us/sq…
Slow BACPAC imports? Use PowerShell to parse SqlPackage.exe logs, spot long-running steps, and find bottlenecks fast, review the Lesson Learned #523: Measuring Import Time -Parsing SqlPackage Logs with PowerShell | Microsoft Community Hub techcommunity.microsoft.com/…
Recently released: Updates to the SqlPackage and the DacFx ecosystem - JSON and VECTOR data types support, parquet support (still in progress), unpack and compare.
techcommunity.microsoft.com/…#dotnet#sqlserver
The key issue here was that a dacpac was being deployed with different versions of SqlPackage. While it would work on ACC with version x, it failed on PRD with version x y. (Due to the time it took to approve ACC vs SqlPackage release cadence)
learn.microsoft.com/en-us/sq…
Correct - I ultimately wanted some better guardrails around schema changes and I can use the SqlPackage DeploymentReport to fail a deploy (and show why) if there's a destructive change