Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-01-30 : 07:19:51
|
| Saleem Subhi writes "I am running SQL 2000 Enterprise SP 3 with Windows 2000 . Our sql server is running around 5 Databases .. we have Pentium IV and RAM 2 GB . SQL Server it self takes more than 1.5 GB to 1.6 GB RAM .. it won't reduce memory consumption as on connection to sql goes down or no one is connected to sql server. SQL Server won't free this ram. we haven't allocated memory for sql server. When we restart the sql server services then the memory consumption goes down to 400 MB. What may be the cause and what can be done to solve it?" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-01-30 : 07:22:46
|
| SQL Server is designed to use as much memory as is available. Once it allocates it, it will not release it. The only control is to set an upper limit on the memory SQL Server can use (say 1 GB). You can do this in Enterprise Manager by right-clicking the server, choosing Properties, and change the settings on the Memory tab. However, if the server is running nothing but SQL Server there is little reason not to allow it to use all of the RAM available. If you are running other processes (like IIS) you should consider moving them off to another machine. |
 |
|
|
|
|
|
Memory management