Retain compression settings when disabling columnstore #8845
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
@akuzm, @Poroma-Banerjee: please review this pull request.
|
Member
|
Currently compression settings imply enabled columnstore so just not deleting it is not enough to implement this functionality |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Retain Compression Settings When Disabling Columnstore
This PR fixes issue #8841 by ensuring that compression settings are preserved when disabling columnstore on a hypertable. Previously, disabling columnstore would delete custom compression settings, preventing users from restoring their configurations when re-enabling columnstore. With this change, settings are retained, allowing seamless restoration.
disable_compressionFixes #8841