August 9, 2011 at 1:24 pm
We have a CRM application which runs on a Windows 2000 Advance Server SP4/ SQL 2000.
Though server and application is running fine, I noticed warning messages on the log when everytime we refreshed the server as follows:
Source Message
------ -------
spid4 Wraning:Unable to allocate 'min server memory' of 7104 MB.
Will this not crashed our system eventually. How do I know what's the min server memory used by our system. What is the recommended setting based on our configurations below:
Our server has the following system summary:
==================================
Total Physical Memory - 7,863,624 KB
Available Physical memory - 5,387,716 kb
Total virtual memory - 17,622,660 kb
Available Virtual memory - 12,992,396 kb
Page File space - 9,759,056 kb
SQL - sp_configure result
===================
name minimum maximum config_value run_value
----------------------------------- ----------- ----------- ------------ -----------
affinity mask -2147483648 2147483647 0 0
allow updates 0 1 0 0
awe enabled 0 1 0 0
c2 audit mode 0 1 0 0
cost threshold for parallelism 0 32767 5 5
Cross DB Ownership Chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
default full-text language 0 2147483647 1033 1033
default language 0 9999 0 0
fill factor (%) 0 100 0 0
index create memory (KB) 704 2147483647 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 32 0 0
max server memory (MB) 4 2147483647 7104 7104
max text repl size (B) 0 2147483647 65536 65536
max worker threads 32 32767 255 255
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 7104 7104
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
open objects 0 2147483647 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
scan for startup procs 0 1 0 0
set working set size 0 1 1 1
show advanced options 0 1 1 1
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0
August 9, 2011 at 6:36 pm
It looks like you have 8GB of RAM in the server and have the min for SQL Server set to 7GB?
I wouldn't set the minimum at all. Leave it at the 128MB or whatever and set the max to be 7GB, or maybe even 6.5GB. This is x86, right?
August 9, 2011 at 7:06 pm
Hi,
Thanks for the immediate response. Below is the info I got from our Server admin. Would it hurt in the long run if we just leave it to that min value like SQL sever/agent will not start, Database crash.
Computer Name: EPIDB
Manufacturer and Model: HP ProLiant ML570 G2
Location Computer: Room / Cabinet #3
Network Operating System:Windows 2000 Adavanced Server
Service Pack :Service Pack 4
Local Admin Password:
Processors : 4 x Intel XEON 3.0GHz
Cache : 4MB
RAM : 8192MB
SCSI Adapters: HP Smart Array 6400
Modems: None
Page Files: C:\ 11518MB
August 10, 2011 at 9:50 am
Set the min low, maybe 1024MB (1GB) and then go from there. The max is usually more important.
If this is x86, 32 bit (and I think it is), then you will need to be sure that you have set up the PAE/AWE settings correctly. This should help you do max memory: http://support.microsoft.com/kb/291988
August 10, 2011 at 3:43 pm
Wil try seting the min to 1024 Mb and leave the max to 7Gb.
Below is how our boot.ini is setup (where PAE is setup). Are there other place to look for PAE settings. Thanks..
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect /PAE
August 12, 2011 at 3:47 am
I would change the max value to 6.5GB just to give the OS that little bit of breathing room, 7GB only leaves 1GB for the OS which isn't much.
Thanks
Chris
August 17, 2011 at 2:31 pm
Thanks.. we set the min/max to 6083 Mb using the option 'used a fixed memory size'. Our server admin is concerned that if we used Dynamic allocation in Sequel 2000 it will used all the memories.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply