SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


memory and CPU allocation on a monster server?


memory and CPU allocation on a monster server?

Author
Message
Warren Peace
Warren Peace
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1325 Visits: 476
Jeffrey & GilaMonster, thanks for the info!!!

fizzlme, sorry for hijacking your post bro.:-)
jjtetzlo
jjtetzlo
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1742 Visits: 5038
Second, for a dedicated database server there is no reason to set a minimum memory amount. Setting the minimum to 12GB and the maximum to 14GB running SQL Server 2005 Standard Edition (x64) will almost certainly cause memory pressure on the system.


Out of curiosity, what is the reason for not setting the minimum memory amount?

Edit: Nevermind... missed Gail's post.

- Jeff
GilaMonster
GilaMonster
SSC Guru
SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)SSC Guru (228K reputation)

Group: General Forum Members
Points: 228601 Visits: 46342
GilaMonster (8/7/2009)
SQL Standard edition cannot use the lock pages in memory feature. It's immaterial that it's an OS setting, the SQL engine cannot and will not use locked pages in anything other than Enterprise edition.


Though it is worth noting that there's a hotfix available (either currently or soon) for both 2005 and 2008, that removes this limitation.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Jeffrey Williams 3188
Jeffrey Williams 3188
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19543 Visits: 10042
Warren Peace (8/7/2009)
Richard, thanks for the vlidation. I know this has always been cunfusing, that's why I raised the question of it.
lol, why the hell does MS leave in there then?......lol Hehe


They leave it in there because that is part of the client-tool which is, of course, used to manage both 64 bit and 32bit systems.

There have been many reports about SQL Server 2005 Standard Edition on x64 paging out memory and memory pressure. What most people have found is that you have to drop the max memory setting quite a bit to relieve these issues. Some have been able to set it as high as 13GB (on 16GB machines) with no problems. Most, however, have not been able to go above 12GB without issues.

I was running Standard Edition on a machine with 32GB of memory. I could not go above 24GB allocated to SQL Server without having memory issues.

Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

fizzleme
fizzleme
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1312 Visits: 335
Just a quick thank you. I will set the maximum at 12 gig with no minimum. This has been extremely informative.

If you find a travel partner without baggage,
Buy a vowel.
Scott Coleman
Scott Coleman
SSCertifiable
SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)

Group: General Forum Members
Points: 7392 Visits: 1532
I had an interesting time at the Seattle PASS conference a few years ago getting some of the Microsoft geniuses behind SQLOS (who insisted that the memory allocation process responds to memory pressure and no max memory setting is necessary) and some other Microsoft geniuses that insisted the other group was nuts. It was very entertaining, but inconclusive.

I would put more faith in the opinions of real-world users, and go with the 12GB recommendation.

The conference is in Seattle again this year but I can't attend. Maybe someone else can get a straight answer.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search