May 13, 2008 at 9:57 am
Yes i agree with you coastliner. 4gb is the way to go, leave the memory setting as it is and sql will use 2gb max.
Ignore all the 3gb boot.ini switch and AWE chat.
If you find the database is struggling after the 4gb has been put in then maybe its time to look at the above options.
ps, definately leave the sql agent running, all your jobs/alerts will need it.
May 13, 2008 at 9:58 am
OK thanks
November 18, 2009 at 10:32 am
The reason for the value is a mathematical one. It is the highest signed 32-bit integer. SQL running on a 32 bit os, 32 bit program, has 32 bit limitations. Essentially 2,147,483,647 just means "the sky is the limit". These values pertain to AWE of course.
If you're running windows server 2003 you must enable physical address extension (PAE) in order for it to recognize more than 4 gb or ram. Enterprise will recognize 32 GB, Datacenter will see 64 GB. You'll notice in the error logs when SQL is started that it only sees 4096 MB of ram. If you want to use more, you need to turn on AWE. There are good articles on technet on how to do this. It will allow SQL server to map areas of memory above the 4GB limit.
2147483647 is also known as the 8th Mersenne prime or in our case... the largest signed 32-bit integer.
Best,
Robert Vandervoort
Helpdesk Analyst / SQL DBA
Harris County Department of Education
Houston, TX
Viewing 3 posts - 46 through 47 (of 47 total)
You must be logged in to reply to this topic. Login to reply