April 6, 2008 at 6:21 pm
Does anybody have any idea why 'Minimum server memory' and 'Maximum server memory' are greyed out in the Server properties screen?
I can change the settings by running the following, but I am just wondering why it won't let me do it via the GUI :crazy:
Thanks.
exec sp_configure 'show advanced options', 1
reconfigure
exec sp_configure 'max server memory (MB)', 1382
exec sp_configure 'min server memory (MB)', 1382
reconfigure with override
April 6, 2008 at 7:37 pm
Are you logged into the GUI as a serveradmin or sysadmin?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 6, 2008 at 7:44 pm
Which edition and service pack of sql server??
April 6, 2008 at 8:32 pm
It's SQL 2005 Ent Edition (64-bit), SP 2.
I am logged in using Windows Auth, my account is set to sysadmin.
April 6, 2008 at 8:50 pm
We have same configuration: SQL Server 2005 64 bit Sp2. And the memory options are not greyed out, yes they are greyed if you click on running values instead of configured.
April 6, 2008 at 10:32 pm
[font="Tahoma"]Hi,
What is the total RAM in the server and how much you are going to assign it SQL server??[/font]
Regards..Vidhya Sagar
SQL-Articles
April 6, 2008 at 10:40 pm
Well 1382 was what was in both boxes, but the server has 4GB of RAM. Wanted to configure it to use 2GB (I am not actually the person setting up this server, the person setting it up in not actually a DBA, they are just upgrading a SAP server so it uses a wizard to do most of the db stuff).
As I said I know I can just change it using sp_configure, so that doesn't fuss me, I was just more curious as to why it won't let me change it via the GUI!
November 4, 2009 at 8:36 pm
I have the same issue on one SQL 2005 St. Edition server (sp3). But on other servers of the same version, the memory settings are not grayed out. Did you ever resolve this?
November 5, 2009 at 12:41 am
try restarting sql server services and login this time using sa account. This would solve your problem
October 18, 2011 at 11:18 pm
Very peculiar - I am getting the same issue as well - just one server - 2008 10.0.4272
Logged in with account that is sa.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 7, 2015 at 5:24 pm
I see this problem when I have sp_configure set to enable the 'set working set size' option. I get the same grayed-out symptom as you saw.
Example to repro:
sp_configure 'set working set size', 100
reconfigure
I believe that the root cause is that in SQL 2005 and above, the 'set working set size' option is not shown in Management Studio for the memory settings page, because it is out of favor as a memory setting, and is not functional in later version of SQL Server. Docs to suggest that are here https://msdn.microsoft.com/en-us/library/ms189056.aspx
When that setting is non-zero, I believe Management Studio grays out the dynamic memory settings (min server memory, max server memory) since the legacy working set options conflicts.
1. Check your current value like this in a query windows in SSMS:
sp_configure 'show advanced', 1
reconfigure
go
sp_configure 'set working set size'
go
Do you see the config_value is non-zero for that setting? (some positive number)
2. If so, (assuming you do not the really old SQL 2000 setting anyway), the workaround is to revert the set working set size back to the default zero.
sp_configure 'show advanced', 1
reconfigure
go
sp_configure 'set working set size', 0
reconfigure
go
sp_configure 'show advanced', 0
reconfigure
Thanks, Jason
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply