Updates_20260901 - Permission to Come Aboard

[erikdarlingdata]

Updates_20260901 — Permission to Come Aboard.

All ten procs move to .9, version date 20260901.

sp_LogHunter stops asking the wrong question

sp_LogHunter refused to run for anyone who was not sysadmin, which was never the permission it actually needed. xp_readerrorlog can be granted with GRANT EXECUTE, and an account holding that grant read the log perfectly well while IS_SRVROLEMEMBER(N'sysadmin') answered no and the proc bailed out.

• The gate is now HAS_PERMS_BY_NAME(N'master.dbo.xp_readerrorlog', N'OBJECT', N'EXECUTE') — the permission the procedure uses, asked about directly. The error message names it too, so a failure tells you what to grant.
• sp_enumerrorlogs, which enumerates the archived logs, is a separate problem: it checks membership in securityadmin itself, and no GRANT substitutes for that. Rather than failing the whole run on error 27219, sp_LogHunter now catches it, reads the current log — which xp_readerrorlog can still do — and says so.

Verified on the reporter's exact permission set, which also proved nothing else in the procedure needs elevation. (#858, #859)

sp_QuickieStore

@find_parameter_sensitive reworked against a production fleet (#854). Ranking is now work-weighted: coefficient of variation alone is scale-blind, and a 3ms→60ms swing was out-ranking a 2s→40s one. On one tenant the window CPU represented by the surfaced top 15 went from 295s to 4,170s. Also: the hash include/ignore lists are honored inside the mode, mixed swings fills a classification gap that left 25 of 162 surfaced shapes with a blank verdict, ratio displays cap at 9999+ instead of printing 2850350x, and the summary now distinguishes "no waits" from "wait capture is off" rather than silently omitting the column.

Two wait-accounting fixes that both understated nothing and overstated everything. @wait_filter matched waits from all of Query Store history rather than the interval asked for (#852), and the wait sort orders counted across all of history the same way (#850).

New log and total log sort orders (#819, thanks @ReeceGoding).

sp_PerfCheck

@database_name narrowed the summary but not the per-file I/O detail, so a filtered run still returned files from every database on the instance — 16 rows where 2 were asked for. The filter is now applied at the sys.dm_io_virtual_file_stats call itself, matching how the Azure SQL DB path already worked, instead of in a WHERE clause that the detail query never had. (#856, #860 — thanks @jbelina)