Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System Memory in Configuration #1131

Open
aachaemenes opened this issue Nov 15, 2024 · 8 comments
Open

System Memory in Configuration #1131

aachaemenes opened this issue Nov 15, 2024 · 8 comments

Comments

@aachaemenes
Copy link

Currently DBA dash under configuration for all the servers shows SQL server settings for MAX and MIN memory. The system memory information is captures under hardware info which is great but If I want to see a quick report on how much ram has been assigned to Windows I have to go back and forth between the tabs. It would fantastic if we can see that info there also. Thanks.

@DavidWiseman
Copy link
Collaborator

I think you might already have what you need on the Hardware tab bar the min server memory. The highlighted column is the max server memory & it calculates how much this is as a % of the physical memory and also what is left for the OS in GB.

image

For min server memory - I would just leave this set to the default value unless you have a good reason to change it. link

@aachaemenes
Copy link
Author

aachaemenes commented Nov 15, 2024 via email

@EsQueEl-Fella
Copy link

I suggest you fix the max amount of the RAM for SQL Server to avoid problems such as the one you mentioned above. What is left over is for Windows (which can get along very well with min 4 GB RAM)

@aachaemenes
Copy link
Author

aachaemenes commented Nov 19, 2024 via email

@DavidWiseman
Copy link
Collaborator

It's not clear exactly what you are asking for but it sounds like you want to know what the current amount of free memory the OS has & identify current issues?
The best way to identify where you have current memory issues across servers - regardless of the max memory configuration, is the performance summary tab. You can add the following performance counters to this summary:
Available Physical Memory (KB) - Current and Min are probably the best aggregations
System Low Memory Signal State - Current and Max are probably the best aggregations

The low signal state should never be 1 - this indicates that the OS is under memory pressure. If this is 1, you might need to reduce max server memory or address whatever is consuming memory on the server if it's not the SQL engine.

The Hardware tab is useful to check the configuration settings are generally appropriate - leaving a percentage of memory free for the OS. As a general rule 10%/4GB for the O/S whichever is greater. If you don't have a dedicated server for 1 instance of the SQL engine, you might need to leave a lot more. I don't think the current available physical memory is really needed on the hardware tab.

@aachaemenes
Copy link
Author

aachaemenes commented Nov 19, 2024 via email

@DavidWiseman
Copy link
Collaborator

As above, you can check the Performance Summary tab. Add these counters in if needed:

Available Physical Memory (KB) - Current and Min are probably the best aggregations
System Low Memory Signal State - Current and Max are probably the best aggregations

You can save the view so they are always displayed & set thresholds on the counters. This identifies servers with issues where you might need to either adjust the max server memory or look at what else is consuming memory on the box.

@aachaemenes
Copy link
Author

aachaemenes commented Nov 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants