Enable WMI For SQL Server Monitoring In Mini DBA

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Windows Management Instrumentation, usually shortened to WMI, lets Mini DBA read Windows host information from a monitored SQL Server machine. SQL Server database monitoring can still work without WMI, but some Windows host counters and process details depend on it.

Mini DBA WMI security settings for SQL Server monitoring

Why Mini DBA Uses WMI

Mini DBA uses SQL Server permissions for database activity, waits, Query Store, cached SQL, error logs, Agent jobs, health checks, and execution plans. WMI is separate from those database permissions. It is used for Windows host information that SQL Server does not expose completely through DMVs.

WMI access can help Mini DBA show:

CPU core performance on the Windows host.
Running Windows process information.
Host-level context for CPU pressure outside SQL Server.
Additional evidence for server resource investigations.

WMI is most useful when you monitor self-managed SQL Server instances on Windows. It is not used for Azure SQL Database because Azure SQL does not expose the underlying Windows host to customers. For Linux SQL Server hosts, use the general Host OS Login guidance instead.

Is WMI Required?

No. WMI is not essential for SQL Server monitoring. If WMI is unavailable, Mini DBA can still collect database-level SQL Server metrics when the monitoring login has the required SQL Server permissions. Pages such as SQL Server Activity, SQL Server Waits, SQL Server Queries, SQL Server Query Store, SQL Server Error Log, and SQL Server Health Checks can still be useful without WMI.

Configure WMI when you want Mini DBA to show richer Windows host CPU and process context, especially when SQL Server CPU appears high but you need to confirm whether SQL Server or another Windows process is using the machine.

Which Account Needs WMI Access?

For SQL Server WMI checks, the Windows account used by the Mini DBA Engine to reach the target Windows server needs remote WMI access. In many deployments this is the Mini DBA Engine service account. If you run the console and engine locally for evaluation, it may be the Windows account running the local Mini DBA process.

Avoid using a local administrator or domain administrator account just to make WMI work. A dedicated domain account or managed service account with targeted WMI and performance counter permissions is a better long-term setup.

Grant Least-Privilege WMI Access

Perform these steps on the Windows server that hosts SQL Server:

Log on to the SQL Server host as a Windows administrator.
Open the WMI Control console by running wmimgmt.msc.
In the console tree, right-click WMI Control and select Properties.
Open the Security tab.
Select Root, then select CIMV2.
Select Security.
Add the Windows account or Windows group used by the Mini DBA Engine.
Grant the account Enable Account and Remote Enable.
Apply the change and close the dialogs.

On some older Windows dialogs or policies, labels may vary slightly. The important point is that the Mini DBA monitoring principal can remotely read the root\cimv2 namespace without being a local administrator.

If your organization manages Windows servers through Group Policy, apply the same WMI namespace permission through your standard security baseline rather than configuring each server manually.

Add Windows Performance Counter Permissions

WMI is only part of Windows host visibility. For the SQL Server permissions modal to show stronger Windows counter coverage, also add the monitoring account to the relevant local groups on the SQL Server host:

Performance Monitor Users.
Performance Log Users.
Event Log Readers, if event or log-based visibility is required by your deployment.

If the server is domain joined, you can add a domain group to those local groups and manage Mini DBA access through group membership.

Check Firewall And Services

Remote WMI needs Windows networking to allow management traffic from the Mini DBA Engine host to the SQL Server host. Confirm:

Windows Management Instrumentation service is running.
Windows Management Instrumentation firewall rules allow the Mini DBA Engine host.
Required RPC traffic is allowed by host firewall and network firewall policy.
Remote Registry is available if performance counter discovery needs it in your environment.

Hardened Windows builds often block remote management by default. If WMI works locally but fails from the Mini DBA Engine, check firewall, RPC, and domain trust before changing SQL Server permissions.

Verify WMI In Mini DBA

After granting permissions, open the SQL Server in Mini DBA and open the SQL Server Connectivity Permissions modal. Select Refresh. The READ WMI check should report OK when the engine can connect to WMI on the target host.

If READ WMI remains NO, database monitoring may still work, but Windows process and CPU core detail may be missing. Use Connectivity Log, Service Log, and Troubleshoot Database Connectivity to separate credential, firewall, and collection errors.

Troubleshooting WMI

If WMI still fails after the permissions change, check these common causes:

The Mini DBA Engine is running under a different Windows account than expected.
The WMI permission was granted on the wrong server or wrong namespace.
The account was added directly but should have been added through a domain group, or the server has not refreshed group membership.
Windows Firewall blocks remote WMI or RPC.
Network firewall rules block RPC between the Mini DBA Engine host and SQL Server host.
The target server is not Windows, or the engine process is running on a platform where Windows WMI collection is unavailable.
Local security policy, UAC remote restrictions, or server hardening policy prevents remote management access.

When troubleshooting, test from the Mini DBA Engine host, not from your workstation, unless your workstation is also the engine host. The network path and Windows identity must match the path Mini DBA uses.

WMI Security Recommendations

Use a dedicated monitoring account or group.
Grant only the WMI namespace and performance counter access Mini DBA needs.
Restrict remote WMI access to the Mini DBA Engine host where possible.
Avoid using local administrator, domain administrator, or personal DBA accounts for routine monitoring.
Review group membership during access reviews and when an engine is moved to a new Windows service account.

WMI FAQ

Does WMI grant database permissions?

No. WMI is Windows host access. SQL Server monitoring still needs SQL Server permissions such as VIEW SERVER STATE, VIEW ANY DATABASE, and VIEW ANY DEFINITION. See Connect SQL Server To Mini DBA for the SQL Server grants.

Why does SQL Server monitoring work but READ WMI says NO?

SQL Server database access and Windows WMI access are checked separately. A SQL login can query SQL Server DMVs without any Windows WMI rights. Conversely, a Windows account can have WMI access without having SQL Server database permissions.

Should I enable WMI on every SQL Server?

Enable WMI where Windows host CPU and process data will help operations. For highly restricted production servers, weigh the extra host visibility against your Windows remote management policy. Mini DBA remains useful without WMI when database permissions are in place.