SQL server enables awe to use large-capacity internal storage

Steps for configuring large memory for zookeeper:

32 GB can be used after large memory is used. It is not clear about more.

Set step values:
1. Install SQL Server2000, upgrade to SP4, and awe patch SQL2000-KB899761-v8.00.2040 installed after SP4, then install a key patch can be, the link is as follows:
Http://support.microsoft.com/default.aspx? Kbid = 899761

2. Set the/PAE threshold in the C:/boot. ini folder, and then restart the host to capture the memory.
3. Run the following commands in SQL query analyzer to activate the awe function of SQL Server (6 GB for this operation ):
Sp_configure 'show advanced options', 1
Reconfigure
Go
Sp_configure 'awe enabled', 1
Reconfigure
Go
Sp_configure 'max Server Memory ', 6000
Reconfigure
Go
Sp_configure 'Allow updates', 1
Reconfigure with override
Go
4. on the Control Panel-Administrative Tools-local security policies-Security Settings-Local Policies-Use Permission assignment in the right pane, select "fixed memory in memory", add a user or group to the user interface of the MSSQLServer server.
[This security setting determines which accounts can use processes to keep data in the physical memory, which prevents the system from paging data to the virtual memory on the disk. Exercise this permission will significantly affect system performance because of reducing the number of available random access memory (RAM).]
5. Run SeCEdit/refreshpolicy machine_policy/enforce or gpupdate In the dig command prompt.
6. Restart the SQL Server Service to make the settings take effect.
7. Run the following commands in SQL query analyzer to check the allow updates function of SQL Server:
Sp_configure 'Allow updates', 0
Reconfigure with override
Go
8. Open a work manager to check whether the user experience is the same as the setting value.

View the version statement: Run select @ version in the query analyzer to view the detailed version number.

Even if all the configurations are correct, the task manager shows that the memory occupied by sqlserver is not the actual memory occupied by sqlserver, which is related to the x86 operating system and cannot be solved, unless you change to an x64 system. The work und is to view the actual amount of memory occupied by SQL Server in the Performance Monitor, where the display is more accurate.

Refer to: http://support.microsoft.com/kb/274750/zh-cnfor how to configure SQL Server to use more than 2 GB of physical memory

Reference: http://tech.sina.com.cn/roll/2007-06-14/1616337275.shtmlSQL server large memory configuration

Reference: http://msdn.microsoft.com/zh-cn/events/ms190673 (SQL .90). aspx enables awe memory for SQL Server

Reference: FAQs about memory Server 2000 awe large-capacity internal storage