Get-DbaMemoryCondition

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

Synopsis

Determine the memory conditions from SQL Server ring buffers.

Description

The information from SQL Server ring buffers can be used to determine the memory conditions on the server when paging occurs.

This command is based on a query provided by Microsoft support. Reference KB article: https://support.microsoft.com/en-us/help/918483/how-to-reduce-paging-of-buffer-pool-memory-in-the-64-bit-version-of-sq

Syntax

Get-DbaMemoryCondition
    [-SqlInstance] <DbaInstanceParameter[]>
    [[-SqlCredential] <PSCredential>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Get-DbaMemoryCondition -SqlInstance sqlserver2014a

Returns the memory conditions for the selected instance

Example: 2

PS C:\> Get-DbaRegServer -SqlInstance sqlserver2014a -Group GroupName | Get-DbaMemoryCondition | Out-GridView

Returns the memory conditions for a group of servers from SQL Server Central Management Server (CMS). Send output to GridView.

Required Parameters

-SqlInstance

The target SQL Server instance or instances.

Optional Parameters

-SqlCredential

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..

-EnableException

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.