September 15, 2006 at 2:59 am
Hi All,
What is the ideal min and max memory setting for the SQL server 2000 on
Apart from the Operating system, they both have got Spotlight installed on them - for monitoring purposes.
I have already done the /3GB setting for the 4GB server. Do we set the min and max for SQL server through the sp_configure procedure, or is there something else as well?
Your help is highly appreciated.
Thanks,
TK
September 15, 2006 at 3:15 am
I assume you're using Enterprise Edition? Otherwise the /3GB setting will have no effect. You don't need to take any further action - SQL Server will manage the memory dynamically.
John
September 15, 2006 at 3:18 am
Yep, for the 4GB server, we are using Enterprise Edition, and the 2GB is standard Edition.
The guys mentioned that they had set the SQL server to fixed memory of 1.7 GB for the 2GB server.
Should I set it to the same as well, through the sp_configure?
September 15, 2006 at 3:22 am
No. Let SQL Server use as much memory it wants. Otherwise there's no point in using the /3GB setting.
John
September 15, 2006 at 4:27 am
Mitchell, Thanks guys I understand that the SQLserver2000 Entyerprise Edn with 4GB of RAM deosn't need any other setting.
What about the SQL server 2000 Standard Edn with 2GB RAM. Do I need to set anything for this server?
September 15, 2006 at 4:42 am
Only if the server is shared with another application that grabs memory like SQL Server does. If your box is dedicated to SQL Server, let SQL Server manage memory dynamically, which is the default.
John
September 15, 2006 at 4:38 pm
Cool! Thanks.
September 17, 2006 at 9:05 pm
As you all suggested, I did not set any max memory limit for my server with 2GB of RAM.
This is just the first day, and it is using 1.88GB out of 2 GB. Only 123 MB is left!
What should I do? Please help!
September 18, 2006 at 1:37 am
That's fine. SQL Server will take as much memory as it needs. If the operating system or another application needs more, SQL Server will give some back. If you have some evidence that performance is being affected by SQL Server having too much memory, then by all means set the max memory to 1.5GB or something like that. If not, best to leave it as it is.
John
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply