SQL Server Performance Forum – Threads Archive

Memory Increase in Cluster

We have 3 SQL Server instances running in cluster.
They had memories 2GB,4GB and 4GB.
They were using max memory upto 1.75GB. We have upgraded the 2GB memory box to 4GB.
Still all 3 of them are not using memory more than 1.78GB. How to make the instances use more memory.

What SQL 2000 version do you have?
Luis Martin
Moderator
SQL-Server-Performance.com Although nature commences with reason and ends in experience it is necessary for us to do the opposite, that is to commence with experience and from this to proceed to investigate the reason.
Leonardo Da Vinci Nunca esperes el reconocimiento de tus hijos, eso ocurrirÃ¡ luego de tu muerte
All postings are provided â€œAS ISâ€ with no warranties for accuracy.

8.00.818 (SP3)

Sorry, I mean SE or EE?.
Luis Martin
Moderator
SQL-Server-Performance.com Although nature commences with reason and ends in experience it is necessary for us to do the opposite, that is to commence with experience and from this to proceed to investigate the reason.
Leonardo Da Vinci Nunca esperes el reconocimiento de tus hijos, eso ocurrirÃ¡ luego de tu muerte
All postings are provided â€œAS ISâ€ with no warranties for accuracy.

I think it is not possible using Cluster in SE.
SQL will use whenever it is memory hungry from operating system.
For more montioring purpose run PERFMON and refer ot KBAhttp://support.microsoft.com/?id=271624 with linkhttp://www.sql-server-performance.com/sg_sql_server_performance_article.asp for furhter help. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

In a 4GB environment you need to add the /3GB switch in boot.ini to take advantage of more than 2GB. http://www.sql-server-performance.com/awe_memory.asp

Can I use /3GB Switch in cluster/failover/san environment? Is there any risk we need consider?

It is EE. Where do I find any white papers/articles on /3GB usage and risks in clustered environment?

http://groups.google.co.uk/group/microsoft.public.windows.server.clustering/browse_thread/thread/d94730f802776859/c0c3addc6275c98d?lnk=st&q=sql+server+%2F3gb+usage+in+clustered+environment&rnum=1&hl=en#c0c3addc6275c98d .. relevant information on few bits and pieces. As Argyle hinted BOL refers
Using AWE Memory on Windows 2000
MicrosoftÂ® SQL Serverâ„¢ 2000 Enterprise Edition uses the Microsoft WindowsÂ® 2000 Address Windowing Extensions (AWE) API to support very large amounts of physical memory. SQL Server 2000 Enterprise Edition can access amounts of memory approaching 8 GB on Windows 2000 Advanced Server and approaching 64 GB on Windows 2000 Data Center. Standard 32-bit addresses can map a maximum of 4 GB of memory. The standard address spaces of 32-bit Microsoft Windows NTÂ® 4.0 and Windows 2000 processes are therefore limited to 4-GB. By default, 2 GB is reserved for the operating system, and 2 GB is made available to the application. If you specify a /3GB switch in the Boot.ini file of Windows NT Enterprise Edition or Windows 2000 Advanced Server, the operating system reserves only 1 GB of the address space, and the application can access up to 3 GB. For more information about the /3GB switch, see Windows NT Enterprise Edition or Windows 2000 Advanced Server Help. AWE is a set of extensions to the memory management functions of the Microsoft Win32Â® API that allow applications to address more memory than the 4 GB that is available through standard 32-bit addressing. AWE lets applications acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space. Although the 32-bit address space is limited to 4 GB, the nonpaged memory can be much larger. This enables memory-intensive applications, such as large database systems, address more memory than can be supported in a 32-bit address space. For more information about AWE, see the MSDNÂ® page at Microsoft Web site. Enabling AWE Memory
You must specifically enable the use of AWE memory by an instance of SQL Server 2000 Enterprise Edition by using the sp_configure option awe enabled. When awe enabled is set to 0, AWE memory is not used, and the instance defaults to using dynamic memory in standard 32-bit virtual address spaces.
When awe enabled is set to 1, AWE memory is used, and the instance can access up to 8 GB of physical memory on Windows 2000 Advanced Server and 64 GB on Windows 2000 Data Center[/]i Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

I am using Windows 2003 R2 + SQL2000 EE as cluster.
I have 5GB RAM installed on both servers.
Still I also have to put the /3GB switch and has to enable AWE option or it is already default due to windows 2003.
Pls reply me?

You need to add /3GB

]]>