-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Comments
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. For min server memory - I would just leave this set to the default value unless you have a good reason to change it. link |
Yes we do but the problem is I have to do back and forth. I have 400
servers. Want to able to see how much ram windows has. We found servers
that only had 2 gb ram left and was causing issues.
…On Fri, Nov 15, 2024, 8:19 AM David Wiseman ***@***.***> wrote:
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.png (view on web)
<https://github.com/user-attachments/assets/c09dc946-390e-4e9e-8eb9-e2baaecf0c65>
For min server memory - I would just leave this set to the default value
unless you have a good reason to change it. link
<https://dba.stackexchange.com/questions/47640/sql-server-min-server-memory>
—
Reply to this email directly, view it on GitHub
<#1131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGN5RX37YLHWVKL4KHZUG7D2AYNJBAVCNFSM6AAAAABR3IWPJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZGM2DCNRSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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) |
I agree but seeing them in the same report makes sense. That's all I am
saying.
…On Tue, Nov 19, 2024, 12:01 AM EsQueEl-Fella ***@***.***> wrote:
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)
—
Reply to this email directly, view it on GitHub
<#1131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGN5RX5WTMTZAAG7DWQNT6D2BLV5FAVCNFSM6AAAAABR3IWPJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUHE3DOOBXGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 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. |
Sorry for the confusion. Let say you have 400 servers. And you want to know
right of the bat which one by mistake has too much memory assigned to SQL
server and windows is almost dying because it has 2 GB ram. How can I see
that quickly in DBA dash in one screen?
…On Tue, Nov 19, 2024, 4:17 AM David Wiseman ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#1131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGN5RX4WH557EGNKUVL7DQT2BMT43AVCNFSM6AAAAABR3IWPJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVGQ4TSOJZHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 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. |
Thanks.
…On Tue, Nov 19, 2024, 7:27 AM David Wiseman ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#1131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGN5RX2QXWR2XVHWUBTPNTL2BNKE5AVCNFSM6AAAAABR3IWPJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGAZDQNBXGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: