Author Chrissy LeMaire (@cl),
Availability Windows, Linux, macOS


Want to see the source code for this command? Check out Get-DbaCpuUsage on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbaCpuUsage.


Provides detailed CPU usage information about a SQL Server's process


"If there are a lot of processes running on your instance and the CPU is very high, then it's hard to find the exact process eating up your CPU using just the SQL Server tools. One way to correlate the data between what is running within SQL Server and at the Windows level is to use SPID and KPID values to get the exact process."

This command automates that process.


Note: This command returns results from all SQL instances on the destination server but the process column is specific to -SqlInstance passed.


    [-SqlInstance] <DbaInstanceParameter[]>
    [[-SqlCredential] <PSCredential>]
    [[-Credential] <PSCredential>]
    [[-Threshold] <Int32>]




Example: 1
PS C:\> Get-DbaCpuUsage -SqlInstance sql2017

Logs into the SQL Server instance "sql2017" and also the Computer itself (via WMI) to gather information

Example: 2
PS C:\> $usage = Get-DbaCpuUsage -SqlInstance sql2017
PS C:\> $usage.Process

Explores the processes (from Get-DbaProcess) associated with the usage results

Example: 3
PS C:\> Get-DbaCpuUsage -SqlInstance sql2017 -SqlCredential sqladmin -Credential ad\sqldba

Logs into the SQL instance using the SQL Login 'sqladmin' and then Windows instance as 'ad\sqldba'

Required Parameters


The target SQL Server instance or instances.

Required True
Pipeline true (ByValue)
Default Value

Optional Parameters


Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential). Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported. For MFA support, please use Connect-DbaInstance.

Required False
Pipeline false
Default Value

Allows you to login to the Windows Server using alternative credentials.

Required False
Pipeline false
Default Value

CPU threshold.

Required False
Pipeline false
Default Value 0

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message. This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting. Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.

Required False
Pipeline false
Default Value False