How much memory is SQL Server 2000 (Standard) supposed to use? I have an installation that has several databases, but the memory footprint of the SQL Server process is 482,000 KB right after the service is started. This sems really high. Does it have to do with the amount of databases in the server? By their size? Is there anything I can do about this? Thanks in advance.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQL Server 2000 Memory
- Thread starter webuser
- Start date
tlbroadbent
MIS
SQL 2000 handles memory dynamically such that memory is acquired and released as needed. Standard Edition can use up to 2GB of memory. SQL Server will use as much memory as possible while still leaving from 4 to 10 MB free for the OS.
Every open database and object, each lock and user connection will use memory. However, the amount of memory used by these items is small compared to the data cache. Most of the memory used by SQL Server is to store data pages in memory so disk IO is reduced.
Unless you are running other applications on SQL Server, which is not good practice, you should allow SQL Server to manage memory dynamically. If other applications are running, you can configure the maximum amount of memory SQL Server uses thus leaving more memory free for other apps.
In other words, the usage you note is not unusual and should be expected. Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
Every open database and object, each lock and user connection will use memory. However, the amount of memory used by these items is small compared to the data cache. Most of the memory used by SQL Server is to store data pages in memory so disk IO is reduced.
Unless you are running other applications on SQL Server, which is not good practice, you should allow SQL Server to manage memory dynamically. If other applications are running, you can configure the maximum amount of memory SQL Server uses thus leaving more memory free for other apps.
In other words, the usage you note is not unusual and should be expected. Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
- Thread starter
- #3
Our usage (in terms of databases/users) is not that high. There are only about 3 databases...2 are used by 2people a piece. The last one is the 'biggie', and is used by about 50 people. But I have the same database running on my local machine, with only me connected, and the SQL Server service is taking up only b/w 1 and 2 MB. Something does not seem right. If I take all the databases offline or detach them, and have all users log off, and then restart the service, should I get a tiny memory footprint until I re-attach the databases? Is this a valid test? Thanks again.
tlbroadbent
MIS
I've never tried the test you suggest. I've not monitored memory usage unless we've had a problem. Unless there are processing problems then I don't see the value in monitoring memory that closely. We want SQL Server to use as much memory as possible. It is much more useful to monitor how SQL Server is using the memory available to it.
You can use performance monitor to monitor many aspects of memory usage. It can show how SQL is using memory.
Are you running the same version of SQL Server on your local machine? If you run MSDE or developer edition on a non-server OS such as Windows 98 or Windows XP, the memory usage algorithm differs from the server OS algorithm so the numbers will usually differ. Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
You can use performance monitor to monitor many aspects of memory usage. It can show how SQL is using memory.
Are you running the same version of SQL Server on your local machine? If you run MSDE or developer edition on a non-server OS such as Windows 98 or Windows XP, the memory usage algorithm differs from the server OS algorithm so the numbers will usually differ. Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
