<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
memory and CPU allocation on a monster...
16 posts, Page 2 of 2
««
1
2
memory and CPU allocation on a monster server?
Rate Topic
Display Mode
Topic Options
Author
Message
Warren Peace
Warren Peace
Posted Friday, August 07, 2009 9:50 AM
SSC Veteran
Group: General Forum Members
Last Login: Monday, February 06, 2012 9:48 AM
Points: 207,
Visits: 450
Jeffrey & GilaMonster, thanks for the info!!!
fizzlme, sorry for hijacking your post bro.
Post #767060
jjtetzlo
jjtetzlo
Posted Friday, August 07, 2009 9:52 AM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 7:44 AM
Points: 1,104,
Visits: 4,568
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
Post #767062
GilaMonster
GilaMonster
Posted Friday, August 07, 2009 10:07 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 12:31 PM
Points: 38,091,
Visits: 30,384
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 2008, MVP
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
Post #767082
Jeffrey Williams 3188
Jeffrey Williams 3188
Posted Friday, August 07, 2009 12:36 PM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Monday, June 10, 2013 12:13 PM
Points: 4,319,
Visits: 9,217
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
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 opportunites brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
Post #767211
fizzleme
fizzleme
Posted Monday, August 10, 2009 10:37 AM
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, December 26, 2012 10:15 AM
Points: 263,
Visits: 183
Just a quick thank you. I will set the maximum at 12 gig with no minimum. This has been extremely informative.
Post #767992
Scott Coleman
Scott Coleman
Posted Wednesday, August 12, 2009 8:42 AM
SSCrazy
Group: General Forum Members
Last Login: Today @ 12:12 PM
Points: 2,819,
Visits: 1,047
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.
Post #769365
« Prev Topic
|
Next Topic »
16 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
