[FEATURE] Review/lower required permission for the Azure server to user database level(no master)

[TrudAX]

Which component(s) does this affect?

• Full Dashboard
• Lite
• SQL collection scripts
• Installer
• Documentation

Problem Statement

Thanks for the tool. I tried to run it (Lite version) for Microsoft Dynamics 365 FO, and currently, it seems the tool requires a full connection to the server itself rather than just to the database.
The issue is that Microsoft provides only a connection to the user database(with full admin rights)
This connection(that they provide) allows viewing TOP queries, deadlocks etc.. if used in the Management Studio

They allow only exec sp_set_database_firewall_rule for the user DB , but not for the master database

But if run your Lite version, it gives that error

and the screen is empty

But I can view TOP queries in Management Studio without master DB access using the same computer/credentials

Proposed Solution

Review queries that are really needed for master DB access and that require only user DB access.
Execute some queries and provide results without master DB access

Use Case

Monitor Databases without require full access to the server. Mostly related to Microsoft D365FO ERP.

I can help in testing if needed

Alternatives Considered

No response

Additional Context

No response

[erikdarlingdata]

Thanks for the detailed report @TrudAX — this is a real issue and we'd like to fix it.

Root cause: On Azure SQL DB, three collectors (query_stats, database_size_stats, file_io_stats) enumerate databases via a connection to master, because sys.dm_exec_query_stats and sys.dm_io_virtual_file_stats are database-scoped on Azure SQL DB (unlike boxed SQL Server, where they're server-scoped). When the login can't open master — as in D365FO — the enumeration fails and the collectors produce nothing.

Fix (PR #858): GetAzureDatabaseListAsync now catches known access-denied/login-failed errors from master and falls back to collecting from the database specified in the connection string only. We cache the fallback decision per server so we don't retry master each collection cycle. Users with master access still get full-server enumeration.

For your D365FO scenario, make sure the Lite connection specifies the user database in the "Database" field when adding the server — that becomes the single-DB target in fallback mode.

I'll ping back when it's merged to dev and available in a build. Happy to have you test it when ready.

[erikdarlingdata]

@TrudAX the fix is merged to dev (PR #858) and will be in the next nightly build. Whenever you're ready to test, pull down a nightly and give it a try — let us know how it goes for your D365FO environment. Reminder: specify your user database in the Database field when adding the server.

[TrudAX]

@erikdarlingdata - now it is better, thank you very much. But can you check Live snapshot button, can it ignore master DB? Right now it is error

[erikdarlingdata]

@TrudAX follow-up fix for the Live Snapshot error is merged to dev (PR #861) and will be in the next nightly build. On Azure SQL Database the query snapshots result set is now scoped to the current database via DB_ID(), which matches the access pattern your D365FO login has — no more cross-database rows that require master access. Give it a try when the nightly lands and let us know.