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 - 2002-09-06 : 09:50:21
|
| Veera Prasad writes "Recently we upgraded our SQL Server 7.0 to SQL 2000. Server configuration is win2k, 2.5 GB RAM and 40 GB Hard disk. Problem is sqlserver.exe is taking the memory nearly around 1.6 GB when we start SQL Server it will be around 40 MB and then it will slow increase the utlization of physical and vertual memory. Atleast once in a week we need to stop and start sql server. We are accessing this database through ASP Pages. Is there any solution to solve this problem if so please inform me as early as possible.RegardsPrasad" |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-09-06 : 10:32:47
|
| This isn't a problem -- SQL Server is supposed to take up as much memory as it can in order to cache up the data. SQL7 used to do the exact same thing. However, if you have other application running on the same box, you might want to limit the maximum amount of memory available to SQL Server. (See description for sp_configure and "max server memory" option in BOL) |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-09-06 : 14:26:23
|
| Please see Memory Architecture in BOL and also INF: SQL Server Memory Usage[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363[/url]HTHJasper Smith |
|
|
|
|
|
|
SQL 2000 Memory Leakage