microsoft / microsoft/DacFx

Ability to ignore DATA_COMPRESSION setting on table/index/partitions

Open
#619 0 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
460
Forks
29
Avg merge
4d 9h
Merged PRs (30d)
7

Description

**Is your feature request related to a problem? Please describe.**
I have a situation where some client production databases have some tables/indexes/partitions where DATA_COMPRESSION has been enabled, but others clients databases where these same items are not using DATA_COMPRESSION.
In order to avoid costly index rebuild operations when deploying newer dacpac builds, I need to clearly indicate that the DATA_COMPRESSION option on indexes/tables/partitions should be ignored.

It _seems_ that the only way to get SqlPackage to ignore DATA_COMPRESSION is by using the **IgnoreIndexOptions** flag. However it is not clear what _other_ options get ignored when this flag is enabled. I am assuming that this ignores _all_ the possible index options.

**Describe the solution you'd like**
Can the options that **IgnoreIndexOptions** controls be clearly documented?
If there is more than one option ignored by this flag, can we have fine-grained control over them? There already seems to be some other flags that control specific index options like **IgnoreIndexPadding**, however its not clear from the documentation how these parameters play together.
Why don't we have an **IgnoreDataCompression** option?

**Describe alternatives you've considered**
The only option we have so far is to use the **IgnoreIndexOptions** and hope that nothing else is being ignored that we're not aware of.

**Additional context**
N/A

Contributor guide

Open the contributing guide

Research direction

Start with the SqlPackage documentation for IgnoreIndexOptions and IgnoreIndexPadding, then trace how DATA_COMPRESSION is handled for tables, indexes, and partitions. Done means documenting which options IgnoreIndexOptions controls and clarifying whether fine-grained control such as IgnoreDataCompression is needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
Domain
databases, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.