[FEATURE]

[mmcdonald-1]

Which script(s) does this affect?

• sp_HealthParser
• sp_HumanEvents
• sp_IndexCleanup
• sp_LogHunter
• sp_PerfCheck
• sp_PressureDetector
• sp_QueryReproBuilder
• sp_QueryStoreCleanup
• sp_QuickieStore
• Other / new script

Problem Statement

With PAGE COMPRESSION being recommended through out for those indexes not yet compressed it brought CPU utilization to mind:

Add another result set for indexes that already have page compression enabled showing the compression success rate. If someone is in a CPU constrained environment one place to look would be page compressed tables with high levels of inserts/updates/deletes. The decision to revert to row compression would be left to the DBA -- Know your environment.

Food for thought.

I'm happy to take a whack....

Cheers

Proposed Solution

Add another result set for indexes that already have page compression enabled showing the compression success rate.

Use Case

Could benefit those in CPU constrained environments. May provide just enough to work out a more suitable solution.

Alternatives Considered

No response

Contribution

• I'm willing to contribute code for this feature

[erikdarlingdata]

@mmcdonald-1 cool, this one is assigned to you. Let me know if you change your mind on it.

[mmcdonald-1]

<working on forking/pull/....>

Here is a modified script to work with. It works with or without the presence of indexes with page compression.

I blocked the section I added starting around line 6669. I'm not sure how you wanted to handle this so here you go.

Cheers

[mmcdonald-1]

On a separate note (I can open another issue if need be) -- The readme.md needs to be updated to include the newly released sort_order parameter.

Cheers

[erikdarlingdata]

@mmcdonald-1 I do appreciate you doing work on things, but submitting code changes like this makes it impossible for me to quickly look at the scope of changes and assess them.

Over in the contributing guide, there's some helpful links and advice on how to contribute to any open source project (including this one). It would involve you submitting a pull request with your changes in it.

I typically handle readme updates when I do releases, so you don't have to worry about including that change here.

[mmcdonald-1]

No worries. That's how they want me to handle things where I work (gitlab) hence my comment. I'll check out the guide and do a pull request. Cheers

…

On Wed, May 6, 2026 at 12:39 PM Erik Darling ***@***.***> wrote: *erikdarlingdata* left a comment (erikdarlingdata/DarlingData#781) <#781 (comment)> @mmcdonald-1 <https://github.com/mmcdonald-1> I do appreciate you doing work on things, but submitting code changes like this makes it impossible for me to quickly look at the scope of changes and assess them. Over in the contributing guide <https://github.com/erikdarlingdata/DarlingData/blob/main/CONTRIBUTING.md>, there's some helpful links and advice on how to contribute to any open source project (including this one). It would involve you submitting a pull request with your changes in it. I typically handle readme updates when I do releases, so you don't have to worry about including that change here. — Reply to this email directly, view it on GitHub <#781 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANLUHMFZMWHOF7AUW3LMQUT4ZNTCNAVCNFSM6AAAAACYRTPC76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJQGE2DENRSGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mmcdonald-1]

I mentioned the readme.md because I see @sort_order in the main branch

Cheers

[mmcdonald-1]

mmcdonald-1@7afd6a0

[erikdarlingdata]

Thanks for sharing the commit link — I can see the work on your fork. When you're satisfied with the changes, please open a pull request against the dev branch (not main) so I can review it properly. The contributing guide has the details if you need a refresher. Appreciate the effort!

[mmcdonald-1]

I'd swear I already did a pull request against dev. I'll check again.

…

On Thu, May 7, 2026 at 1:54 PM Erik Darling ***@***.***> wrote: *erikdarlingdata* left a comment (erikdarlingdata/DarlingData#781) <#781 (comment)> Thanks for sharing the commit link — I can see the work on your fork. When you're satisfied with the changes, please open a pull request against the dev branch (not main) so I can review it properly. The contributing guide has the details if you need a refresher. Appreciate the effort! — Reply to this email directly, view it on GitHub <#781 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANLUHMCFJ27Y2ZU6CYRORV34ZTEVBAVCNFSM6AAAAACYRTPC76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJZG4YTENZTGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[erikdarlingdata]

@mmcdonald-1 a gentle poke to see if you still wanted to contribute this code.

[mmcdonald-1]

I do but it still shows that I have a pull request and I cannot make another one. I can try to clone again and do another pull request maybe that will work? Martin

…

On Mon, May 18, 2026 at 10:38 AM Erik Darling ***@***.***> wrote: *erikdarlingdata* left a comment (erikdarlingdata/DarlingData#781) <#781 (comment)> @mmcdonald-1 <https://github.com/mmcdonald-1> a gentle poke to see if you still wanted to contribute this code. — Reply to this email directly, view it on GitHub <#781 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANLUHMF66D7W2KZCFMI22R343MN6BAVCNFSM6AAAAACYRTPC76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZYG42DKNJUGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[erikdarlingdata]

@mmcdonald-1 what has likely happened is that you've opened a pull request against your local fork and not mine. You can sometimes change that, or you can close it and start a new one pointed at my dev branch. If you point it at main it will be automatically denied.