Skip to content

sp_Blitz: stop flagging version high/low part of SQL Server configs (#4022) - #4023

Closed
BrentOzar wants to merge 1 commit into
devfrom
4022_sp_Blitz_bad_defaults
Closed

sp_Blitz: stop flagging version high/low part of SQL Server configs (#4022)#4023
BrentOzar wants to merge 1 commit into
devfrom
4022_sp_Blitz_bad_defaults

Conversation

@BrentOzar

Copy link
Copy Markdown
Member

Fixes #4022

Problem

sp_Blitz reported version high part of SQL Server and version low part of SQL Server under Non-Default Server Config (CheckID 22). These two sp_configure options have no meaningful "correct" value — they encode the build number — so sp_Blitz should never alert on them no matter what they're set to.

They were originally added to the #ConfigurationDefaults list in #3657 with hard-coded "defaults" of 1114112 / 52428803. On any server where the actual values differ from those magic numbers (e.g. the reporter set them to 0, which Microsoft documents as the default), CheckID 22's WHERE cdUsed.name IS NULL predicate fired and flagged them.

Fix

Remove both entries from #ConfigurationDefaults. Because CheckID 22 uses an INNER JOIN #ConfigurationDefaults cd ON cd.name = cr.name, a config that isn't in the list can never be reported — exactly the desired behavior.

This was already done for sp_Blitz.sql in #3906, but the matching lines in Install-All-Scripts.sql regressed (re-introduced by a later regeneration), leaving the two files out of sync. This PR resyncs Install-All-Scripts.sql.

Testing

Verified on a live instance (sys.configurations reports both options with value/value_in_use = 0, configuration_id 1593/1594). With these entries absent from #ConfigurationDefaults, neither option appears in the Non-Default Server Config findings regardless of its value.

🤖 Generated with Claude Code

These two sp_configure options ('version high part of SQL Server' and
'version low part of SQL Server') have no "correct" value, so sp_Blitz
should never flag them under Non-Default Server Config no matter what
they're set to. They were removed from sp_Blitz.sql in PR #3906, but the
matching lines in Install-All-Scripts.sql regressed via a later
regeneration. This resyncs Install-All-Scripts.sql with sp_Blitz.sql.

Removing them from #ConfigurationDefaults means CheckID 22's INNER JOIN
no longer matches them, so they're never reported. Fixes #4022.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 15, 2026 14:53
@BrentOzar BrentOzar closed this Jun 15, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aligns the installer script with sp_Blitz behavior by removing the two SQL Server “version part” sp_configure options from the seeded #ConfigurationDefaults list so they are no longer eligible to be flagged by CheckID 22 (Non-Default Server Config).

Changes:

  • Removed version high part of SQL Server from #ConfigurationDefaults in the installer script.
  • Removed version low part of SQL Server from #ConfigurationDefaults in the installer script.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@BrentOzar
BrentOzar deleted the 4022_sp_Blitz_bad_defaults branch July 2, 2026 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sp_Blitz: Configuration parameters have wrong Defaults set

2 participants