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



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


Calculates the recommended value for SQL Server 'Max Server Memory' configuration setting. Works on SQL Server 2000-2014.


Inspired by Jonathan Kehayias's post about SQL Server Max memory (, this script displays a SQL Server's: total memory, currently configured SQL max memory, and the calculated recommendation.

Jonathan notes that the formula used provides a general recommendation that doesn't account for everything that may be going on in your specific environment.


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




Example: 1
PS C:\> Test-DbaMaxMemory -SqlInstance sqlcluster,sqlserver2012

Calculate the 'Max Server Memory' for SQL Server instances sqlcluster and sqlserver2012

Example: 2
PS C:\> Get-DbaRegServer -SqlInstance sqlcluster | Test-DbaMaxMemory

Calculate the 'Max Server Memory' settings for all servers within the SQL Server Central Management Server "sqlcluster"

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

Find all servers in CMS that have Max SQL memory set to higher than the total memory of the server (think 2147483647) and set it to recommended value.

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

Windows Credential with permission to log on to the server running the SQL instance

Required False
Pipeline false
Default Value

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