< Back
Get-DbaCpuUsage
Post
NAME Get-DbaCpuUsage
SYNOPSIS
Provides detailed CPU usage information about a SQL Server's process
SYNTAX
Get-DbaCpuUsage [-SqlInstance] <Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-SqlCredential]
<Pscredential>] [[-Credential] <Pscredential>] [[-Threshold] <Int>] [-EnableException <Switch>]
[<CommonParameters>]
DESCRIPTION
"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.
References:
https://www.mssqltips.com/sqlservertip/ ... lly-using/
Note: This command returns results from all SQL instances on the destination server but the process
column is specific to -SqlInstance passed.
PARAMETERS
-Credential [<Pscredential>]
Allows you to login to the Windows Server using alternative credentials.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-EnableException [<Switch>]
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
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-SqlCredential [<Pscredential>]
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
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-SqlInstance [<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]>]
The target SQL Server instance or instances.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Threshold [<Int>]
CPU threshold.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
NOTES
Tags: CPU
Author: Chrissy LeMaire (@cl), netnerds.net
Website: https://dbatools.io
Copyright: (c) 2018 by dbatools, licensed under MIT
License: MIT https://opensource.org/licenses/MIT
-------------------------- 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'
RELATED LINKS
https://dbatools.io/Get-DbaCpuUsage
SYNOPSIS
Provides detailed CPU usage information about a SQL Server's process
SYNTAX
Get-DbaCpuUsage [-SqlInstance] <Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]> [[-SqlCredential]
<Pscredential>] [[-Credential] <Pscredential>] [[-Threshold] <Int>] [-EnableException <Switch>]
[<CommonParameters>]
DESCRIPTION
"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.
References:
https://www.mssqltips.com/sqlservertip/ ... lly-using/
Note: This command returns results from all SQL instances on the destination server but the process
column is specific to -SqlInstance passed.
PARAMETERS
-Credential [<Pscredential>]
Allows you to login to the Windows Server using alternative credentials.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-EnableException [<Switch>]
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
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-SqlCredential [<Pscredential>]
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
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-SqlInstance [<Sqlcollaborative.Dbatools.Parameter.DbaInstanceParameter[]>]
The target SQL Server instance or instances.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
-Threshold [<Int>]
CPU threshold.
Required? false
Position? named
Default value
Accept pipeline input? False
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
NOTES
Tags: CPU
Author: Chrissy LeMaire (@cl), netnerds.net
Website: https://dbatools.io
Copyright: (c) 2018 by dbatools, licensed under MIT
License: MIT https://opensource.org/licenses/MIT
-------------------------- 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'
RELATED LINKS
https://dbatools.io/Get-DbaCpuUsage