Sqlpackage shows a discrepancy on data compression when new partition is created
@ssreerama is already working on this.
Since Mar 22, 2023.
- Dominant language
- C#
- Stars
- 460
- Forks
- 29
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Description
- SqlPackage or DacFx Version: 161.8089.0
- .NET Framework (Windows-only) or .NET Core: .NET Framework
- Environment (local platform and source/target platforms): Windows
**Steps to Reproduce:**
Full steps and example solution can be found in my repo https://github.com/DotdigitalDBA/sqlPackageTickets/tree/main/PartitionCompressionIssue
Basic Repro steps are below but ensure you check the repo above for detailed steps
1. Partitioned table in source control using data compression=page syntax (meaning page compression on all partitions)
2. Data moves on and an outside process creates extra partitions
3. SSDT Shows data compression on every partition in source control and shows the extra partition as a discrepancy on the table
4. SSDT will now constantly see this data compression on a new partition as a discrepancy
5. Its not feasible to change source control every time a new partition is created as this is fluid and automated at different times for different tables.
6. This causes Sqlpackage to do whole table rebuilds to “fix” when nothing is actually wrong. This can block up our app as it tries to do it on 4tb tables
**Did this occur in prior versions? If not - which version(s) did it work in?**
(DacFx/SqlPackage/SSMS/Azure Data Studio)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.