-
Notifications
You must be signed in to change notification settings - Fork 174
Description
Version of the script
Look in the stored procedure, and it'll have a version date & number near the top. Put that in here. If it's not the current version (dated in the last month), then upgrade to the current version and test that before reporting a bug - we fix a lot of stuff in each new build. We'll flat out close bug reports for older builds.
version = 1.6
version_date = 20250601
What is the current behavior?
(Lines 3471 to 3473, check_id = 7006)
The following details text contains line breaks, which cause unintended row breaks when copying the output of sp_PerfCheck into Excel:
details = N'Query Store is not enabled.
Consider enabling Query Store to track query performance
over time and identify regression issues.',
If the current behavior is a bug, please provide the steps to reproduce.
This is not really a functional bug, but rather a formatting issue. When the result set is copied into Excel, the embedded line breaks cause misaligned cells.
What is the expected behavior?
Remove the line breaks from the details field.
As a workaround, I replaced the text with concatenated strings:
details = N'Query Store is not enabled.'
+ N' Consider enabling Query Store to track query performance'
+ N' over time and identify regression issues.',
This avoids line breaks and preserves readability when pasting into Excel.
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
SQL Server 2019
IMPORTANT: If you're going to contribute code, please read the contributing guide first.
https://github.com/erikdarlingdata/DarlingData/blob/main/CONTRIBUTING.md
I am only providing feedback on the formatting issue, not contributing code changes.