Get-DbaMaxMemory

Synopsis

Retrieves SQL Server max memory configuration and compares it to total physical server memory

Description

This command retrieves the SQL Server ‘Max Server Memory’ configuration setting alongside the total physical memory installed on the server. This comparison helps identify potential memory configuration issues that can impact SQL Server performance.

Use this function to audit memory settings across your environment, troubleshoot performance issues related to memory pressure, or verify that SQL Server isn’t configured to use more memory than physically available. The function is particularly useful for finding instances with the default max memory setting (2147483647 MB) that should be properly configured based on available physical memory.

Results are returned in megabytes (MB) for both the configured max memory and total physical memory values.

Syntax

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

Examples

Example: 1

PS C:\> Get-DbaMaxMemory -SqlInstance sqlcluster, sqlserver2012

Get memory settings for instances “sqlcluster” and “sqlserver2012”. Returns results in megabytes (MB).

Example: 2

PS C:\> Get-DbaRegServer -SqlInstance sqlcluster | Get-DbaMaxMemory | Where-Object { $_.MaxValue -gt $_.Total }

Find all servers in Server Central Management Server that have ‘Max Server Memory’ set to higher than the total memory of the server (think 2147483647)

Example: 3

PS C:\> Find-DbaInstance -ComputerName localhost | Get-DbaMaxMemory | Format-Table -AutoSize

Scans localhost for instances using the browser service, traverses all instances and displays memory settings in a formatted table.

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.