[BUG] SQL 2016 Passive Server for Mirror (SQL Dumps on Latest 2.2.0 version)

[jaywiseman1971]

Component

SQL collection scripts

Performance Monitor Version

2.2.0

SQL Server Version

SQL 2016

Windows Version

Windows Server 2019

Describe the Bug

Passive Server Dumps v2.2.0.zip

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Steps to Reproduce

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Expected Behavior

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Actual Behavior

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Attached Dumps.

Error Messages / Log Output

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Screenshots

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

Additional Context

Bug is back from being fixed by changing the default user to a NON mirrored database with v2.2.0.

[erikdarlingdata]

@jaywiseman1971 Thanks for the report and the dump files — they confirmed this is the same root cause as #384 and #430.

The new FinOps collectors (database size stats and server properties) added in v2.2.0 iterate databases using cursor-based dynamic SQL, but were missing the defensive filters that the other collectors already had. Specifically, the server properties collector was missing the HAS_DBACCESS() check entirely, so on your mirroring passive server it was trying to access the RESTORING database and triggering the severity 22 engine crash.

Fixed in PR #537 — both collectors now use d.state = 0 and HAS_DBACCESS() to match the pattern from the earlier fix. This will be in the next release. For now, you can use the updated scripts to validate the fix.