Home > Ask the SQL Server Experts > Archive: Performance Tuning Questions & Answers > How to increase server memory used in SQL Server 2000
Ask The SQL Server Expert: Questions & Answers
EMAIL THIS

How to increase server memory used in SQL Server 2000

Denny Cherry EXPERT RESPONSE FROM: Denny Cherry

Pose a Question
Other SQL Server Categories
Meet all SQL Server Experts
Become an Expert for this site


Expert advice on database administration
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 10 December 2007
I'm using SQL Server 2000 Enterprise Edition and finding the total server memory is 1670976. The target server memory is also 1670976. My question is, if the server has 3GB of RAM, why is it that this value doesn't change much when the server is under I/O or CPU pressure? Why does it seem like the amount of memory used stays constant?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Archive: Performance Tuning
Upgrading to SQL Server 2008 advantages and hardware requirements
Tool to synchronize two SQL Server databases
Performance tuning for SQL Server 2005 and Exchange running on SBS
SQL Server tools don't appear in menu after SQL Server 2005 install
Use SQL Profiler to find long running stored procedures and commands
Maintain large SQL Server database and resolve website 'Timeout Error'
How to retrieve SQL Server database disk space in use
Troubleshoot SQL Server 2005 temporary table performance problems
View query execution plan in SQL Server with this method
Adding non-clustered indexes to SQL Server columns

Microsoft SQL Server Performance Monitoring and Tuning
Performance implications of transaction log autogrowth in SQL Server
The short course on how SQL Server really works
Determining the source of full transaction logs in SQL Server
Improving SQL Server full-text search performance
New GROUP BY option provides better data control in SQL Server 2008
Microsoft SQL Server 2008 Resource Governor primer
Examining data files when SQL Server tempdb is full
Testing transaction log autogrowth behavior in SQL Server
Meeting business needs with SQL Server full-text search
Using dynamic management views to improve SQL Server index effectiveness

SQL Server High Availability, Scalability and Reliability
Top load balancing methods for SQL Server
Maintaining high availability of SQL Server virtual machines
Creating fault-tolerant SQL Server installations
Scaling up vs. scaling out with SQL Server 2008
How to configure storage in SQL Server database with more writes than reads
SQL Server database replication tutorial
Licensing a standby server for SQL Server replication
Get SQL Server log shipping functionality without Enterprise Edition
Monitor database mirroring and replication after a SQL Server upgrade
Upgrade live applications to SQL Server 2005 for high availability
SQL Server High Availability, Scalability and Reliability Research

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
contiguity  (SearchSQLServer.com)
contiguous  (SearchSQLServer.com)
drilldown  (SearchSQLServer.com)
hashing  (SearchSQLServer.com)
hybrid online analytical processing  (SearchSQLServer.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


The target server memory is the maximum amount of memory that the server is configured to use. The total server memory is the amount of memory the server is using. Based on the numbers you've provided, your server is set up to use about 1.6 Gigs of memory. In order to increase this closer to the 3 Gigs of memory you have installed, you will want to make sure sp_configure shows SQL Server is set up to use more than 2 Gigs of memory. You'll also need to enable AWE to go past 2 Gigs of memory.

In addition, your operating system will need to be Windows 2000 Enterprise Edition or Windows 2003 Standard or Enterprise edition. If your OS is one of these, enable PAE using the /PAE switch in the boot.ini file. Changes to the boot.ini file will require that the server be rebooted to take effect. You should read Microsoft article, How to edit the Boot.ini file in Windows XP before editing the boot.ini file.



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



SQL Solutions - SQL Database Design
HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2005 - 2009, TechTarget | Read our Privacy Policy 		  TechTarget - The IT Media ROI Experts