microsoft / microsoft/DacFx

EnableFastComparison succeeds despite changes to postdeploy.sql

Open
#826 1 comment 0 reactions 0 assignees View on GitHub
bug fastcomparison
Dominant language
C#
Stars
460
Forks
29
Avg merge
4d 9h
Merged PRs (30d)
7

Description

- SqlPackage or DacFx Version: latest preview
- .NET Framework (Windows-only) or .NET Core: sqlpackage 170.5.60.2
- Environment (local platform and source/target platforms): Windows

**Steps to Reproduce:**

1. Create a Microsoft.Build.Sql project with a single table and a postdeploy.sql script
2. Publish with EnableFastDeploy and see FastDeploy kick in on second run.
3. Update the post deploy script and rebuild the .dacpac
4. Expected: Full deployment, actual: FasTDeploy kicks in.

Contributor guide

Open the contributing guide

Research direction

Reproduce the behavior with a Microsoft.Build.Sql project containing a table and postdeploy.sql: publish with EnableFastDeploy, modify the script, and rebuild the dacpac. Trace the EnableFastDeploy comparison path first; done means the changed postdeploy.sql causes a full deployment rather than FastDeploy on the second publish.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
Domain
databases, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.