March 16, 2009 at 5:54 am
hello,
I have two instances mssql 2000 sp4 on windows 2003.
memory installed on server 8 GB
I allocated fixed size 3.5GB RAM for each instance but I still show in error log the message " unable to allocate min server memory 3500MB"
What I ca do to avoid this warning?
Thanks in advance,
Hadrian
March 16, 2009 at 6:08 am
If you are not using the 64 bit edition, you can’t use more the 2GB without configuring the server to use awe. If you are not using Enterprise edition, you can’t configure AWE, so in order to use more then 2GB you need to run SQL Server 64 bit or use SQL Server enterprise edition and configure it to use AWE. Can you let us know if you are using 64 bit or enterprise edition and if you configured the server to use AWE?
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 16, 2009 at 7:21 am
it's 32 bit
first I configurated AWE but because I put only 3.5 GB for each instance I disable AWE.
March 16, 2009 at 7:33 am
If I understand you correctly, both instances are not configured to use awe. If this is the case, none of them will be able to use more then 2GB. If I didn’t understand you, can you pleas explain your situation again?
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 16, 2009 at 8:16 am
yes you are right the instances are not configurated with AWE because I was thinking that AWE is for > 4GB and I choose only 3.5GB.
anyway If I eanble AWE the mssql need restart?
March 16, 2009 at 9:02 am
After your last message, I looked for more information instead of using my memory, and I have to say, that you might be correct. When windows 2000 is used, you need to use awe if you want to use more then 2GB of memory, but I’m not sure that this is also the case when you use windows 2003. Unfortunately the part about windows 2003 was not very clear. Since I’m not sure that I understand it correctly, I suggest that you’ll also have a look at the KBarticle from Microsoft (http://support.microsoft.com/kb/274750).
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 17, 2009 at 4:19 am
You will need to have the /PAE and /3GB switch in boot.ini and AWE active on SQL Server in order to get the memory use you want.
I think most of the discussions about the need for AWE when you want to use more than 4GB memory assume you only have 1 SQL instance on the box. If you have multiple instances and want to use more than 4GB in total then this can only be done by using AWE.
You need to be aware of how SQL Server will use the available memory. It is only the SQL buffer pool that can be placed in AWE memory, and even then only part of it is in AWE memory. All the rest of SQL memory must live below the 4GB line.
Within this 4GB limit, you need to find space for Windows, SQL Server, plus anything else you run (e.g. anti-virus, DB backup jobs, etc). If you have the /3GB switch you limit Windows to using only 1 GB memory, leaving 3 GB for everything else. You probably need to allow 0.5 GB (or more) for the non-SQL Server things on the box, leaving 2.5 GB to share between the two instances. This should be ample unless SQL Server is heavily loaded.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 17, 2009 at 5:28 am
so for 8GB RAM installed I choose for each of the twon instances 3.5Gb,in total 7 GB remains 1 GB for Windows, AWE enabled.It is the right allocation?
March 17, 2009 at 6:01 am
Asking for 3.5 GB for each instance is probably more memory than is available. You will need to experiment with values between 3GB and 3.5 GB to see what works. It is possible that only 1 instance may be able to get the AWE memory, you will have to try and see what happens.
SQL Server will make only 1 attempt at getting the memory. If it is not available at that point in time you will not get your AWE memory. The Windows component that satisfies the memory request is sensitive to memory being fragmented. This can be an issue if you have to restart SQL Server after it has been running for a while. Memory below the 4GB line can get fragmented to the extent that SQL Server is unable to get the memory it asks for at a restart when it can gt it just after a reboot..
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 17, 2009 at 7:26 am
Thanks for interesting AWE issues.
If I use only 3.5Gb for an instance with AWE enabled for it , could I leave the second without AWE?
March 17, 2009 at 9:10 am
Yes, you can have 1 instance with AWE and 1 without. You should try various combinations to see what works best for you.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy