June 4, 2013 at 4:13 am
Spotted this in SQL ERROR log
"SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure."
So off I went
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 3072
RECONFIGURE
GO
Configuration option 'min server memory (MB)' changed from 0 to 1024. Run the RECONFIGURE statement to install.
Configuration option 'max server memory (MB)' changed from 2147483647 to 3072. Run the RECONFIGURE statement to install.
Did I do the right thing? Its only a laptop with 4GB of memory! Why was i set at 2147483647 ? I think I have seen 2147483647 as the MAX memory before.
Am I ngoing bonkers or is this some kind of forgot to convert to MB kind of issue?
Cheers
E
June 4, 2013 at 5:11 am
Ells (6/4/2013)
Spotted this in SQL ERROR log"SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure."
The message said to set the awe enabled option, not max server memory. However if it's just a development laptop, there's probably no need and having sQL use no more than 1.7GB (limit without AWE) is probably OK.
Why was i set at 2147483647 ? I think I have seen 2147483647 as the MAX memory before.
It's the default.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply