SQL Server Performance Forum – Threads Archive

RAM Optimization 3GB and PAE

I have a SQL server with 8GB on Win2k Advanced SP2 and SQL2000 with SQL SP2. At present system is configured with /3GB and /PAE. With this /3GB, the OS gets restricted to 1GB and causes intermittent OS 1450 errors. One can do system tunning but can take lot of time and may be fatal or not fruitful. Does anyone know if we can just use /PAE and remove /3GB? By doing this, atleast we will have 2 GB for opreating system and 6 GB for SQL and that will address OS1450. Thanks in advance

If you mean: http://support.microsoft.com/default.aspx?scid=kb;en-us;291228 Apply sp3. Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

I think you have to remove /3GB when using /PAE. Gaurav
Moderator
Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard
The views expressed here are those of the author and no one else. There are no warranties as to the reliability or accuracy of anything presented here.

Thanks for the input. I am sorry the OS service pack was SP3 on the server. But it is the case here, as we are running low on kernel memory. Regarding /3gb that’s what I really want to know for sure. I came across some MS articles where they hinted to use /3gb if application needs to take advantage of the memory above 4 GB. I will post the URL. In essence, use both. I will post the article and we can have opinion on the article.

How about settings of memory on the SQL?
http://www.winnetmag.com/Windows/Article/ArticleID/15532/15532.html fyi. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Yeah, I don’t think it’s your BOOT.INI setting that are the problem. In SQL Server, you need to make sure you are not using dynamic memory. I usually set both my min and max size to 1gb or 1.5gb under the total memory I have on a dedicated SQL Server box and have never had this error because of it. Set the min and max to the same size so SQL Server automatically reserves that memory and uses as needed. MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.

Thanks all for additional input and will try them.Here is the article that I promised to post: http://support.microsoft.com/default.aspx?scid=kb;EN-US;283037
Here is some thing more interesting and that is Win2k SP4. It addresses reduction in Pool memory. Infact Win2k Sp4 has fixed many problems related to Memory leaks, Pool memory, Cluster services, multipath to SAN/Storage device. http://support.microsoft.com/default.aspx?kbid=811732 Win2k SP4: http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/default.asp

]]>