[BUG] Collection-procedures @debug=1 does not return any info

[ghauan]

Component

Full Dashboard

Performance Monitor Version

2.10.0

SQL Server Version

sql server 2025 (and probably others)

Windows Version

Windows Server 2019

Describe the Bug

In the PerformanceMonitor-database if I run a collection-procedure with the @Debug-flag set to 1, I do not get any printed information returned to the Messages-tab. I have seen/tested this with [collect].[cpu_utilization_stats_collector] , but the problem probably is in other collect-procedures as well.

Steps to Reproduce

In SSMS run EXEC [collect].[cpu_utilization_stats_collector] @debug=1

Expected Behavior

In the Messages tab, I would expect to see something like:
Collected 1 CPU utilization stats rows

Actual Behavior

I only get the following:
Commands completed successfully.

Error Messages / Log Output

Screenshots

No response

Additional Context

The problem originates in that %d expects integer while the variable @rows_collected is bigint.

If changed from:
RAISERROR(N'Collected %d CPU utilization stats rows', 0, 1, @rows_collected) WITH NOWAIT;

to:
RAISERROR(N'Collected %I64d CPU utilization stats rows', 0, 1, @rows_collected) WITH NOWAIT;

...it works.

[erikdarlingdata]

Thanks for the report — and for the spot-on diagnosis. You were exactly right: RAISERROR's %d substitution accepts only int, and @rows_collected is declared bigint (set from ROWCOUNT_BIG()), so the message rendered as nothing.

This wasn't just cpu_utilization_stats_collector — the same pattern was in every collector's @debug=1 row-count line, plus a few other bigint arguments elsewhere. Fixed all of them: 35 %d → %I64d substitutions across 31 install files. Multi-argument calls were handled positionally, so %d stays where the argument is genuinely an int.

To be clear for anyone finding this later: it was a diagnostic-output bug only. The SQL Agent collection jobs never pass @debug=1, so actual data collection was never affected — the messages were just invisible when a collector was run by hand.

Verified with a full install against SQL Server 2022 and a manual run:

EXEC collect.cpu_utilization_stats_collector @debug=1;
-- Collected 1 CPU utilization stats rows

The fix is merged and will go out in the next release. Closing this out — thanks again.