-
sql 2000 mem setting versus real memory
I have a client server that has win2000 on it with sql 2000 enterprise edition. The box has 4 gig of memory on it. I noticed today that the sql server was set to use all 4 gig (even though I know sql can't really access that memory because sql can't really utilize the 2-4 gig range). Is there overhead or a downside to leaving it at this, or should I set it to 2 gig
-
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000 Developer Edition can use up to 2 GB of physical memory. With the use of the AWE enable option, SQL Server can use up to 4 GB of physical memory.
Note You cannot allocate more than 4 GB of physical memory to an application on Windows 2000 Server because Physical Address Extension (PAE) is not available on Microsoft Windows 2000 Server. Also, you cannot use the 3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000 Advanced Server or Microsoft Windows Datacenter versions.
Full article can be found at:
http://support.microsoft.com/kb/274750
and
http://support.microsoft.com/kb/291988/
--HTH--
-
That's what I thought, since they are not running advanced server, really can't use more than 2. I was just wondering since the sql max memory is at 4 gig if that would cause any issues
-
Will not affect performance in this case. By the way, SQL Server 2000 Enterprise Edition can use 3gb memory on Windows 2000 Advanced Server if you put /3gb in boot.ini file. With awe enabled, sql2k enterprise edition can use more than 3gb memory on win2k advanced server with more than 4gb memory and has /pae in boot.ini file.
Last edited by rmiao; 11-03-2006 at 04:59 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|