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-05-01 : 08:57:49
|
| george writes "Hi,we have 1024mb of physical memory available on the server.other than sql server 2000 it will be another application running on the server (weblogic). my question is:How much memory should i set up for sql server 2000 to be safe?Thank you,George" |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-05-01 : 09:21:36
|
| Come on George . . . there is not magic number (other than the minimum recommendation, which you are above) . . . if you have a performance problem, figure out what the bottleneck is and fix that . . . you will never hurt the box by adding more memory . . . what is your definition of 'safe'? . . . when in doubt, put in as much memory as you can afford . . .<O> |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-05-02 : 08:09:23
|
| Depending on the amount of data, you are already at a disadvantage by running another application server on the same machine. SQL Server doesn't work well when other applications are fighting for memory, at least not when the system is storing lots of data and has a high frequency of users. Having 1gb of RAM is a good starting place for SQL2000, but you'll need to test performance with a realistic load (both data and users) to get a true sense of how the system will perform in the "real-world". Testing is crucial. Keep in mind that memory isn't the only factor in SQL Server performing well. The processors (and number of processors) matters considerably, and probably one of the most important aspects is your disk subsystem. Having a slow read/write disk subsystem will ruin performance.Good luck.Kyle Heon, MCPPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
|
|
|