Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database performance issue


Database performance issue

Author
Message
Fidel Rodriguez
Fidel Rodriguez
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 192
Hmm... I think the number you're looking for will be based on the SLA / user experience you're bound to deliver. I also think that the exact number you're looking for is dynamic in nature as it will change over time as the database grows. Once you determine the level of performance you want to deliver---and can meet that given the hardware you have, allocate your resources such that you meet your goals. If you can exceed them, perhaps you can do so until the spare resources are needed by other databases seeking a home. Use the page life, query response, cache hit ratio and other metrics listed earlier along with execution plans to find out what you're working with.
---FR
BaldingLoopMan
BaldingLoopMan
Old Hand
Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)Old Hand (312 reputation)

Group: General Forum Members
Points: 312 Visits: 457
mem settings
• If server memory is <= 3 GB, set min memory to 1 GB, and max memory to server less 512 MB.
• If server memory is > 3 GB, settings depend on the server platform (32-bit or 64-bit), presence of /3 GB in the boot.ini and on usage of AWE.
• For servers on 64-bit platform AWE is not required, and min memory should be server memory less 2 GB, max memory – server memory less 1 GB.
• On 32-bit platform with AWE : min memory and max memory should be server memory less 1 GB; without AWE – if /3 GB switch is not used, max memory = 2 GB, with the switch it is 3 GB (with min memory 1 GB less than that).
Tim Weintz
Tim Weintz
SSC-Enthusiastic
SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)

Group: General Forum Members
Points: 158 Visits: 147
1. Are both builds of SQL the same?
2. Do the execution plans look the same?
3. How are you comparing response times between the two systems?
Nicholas Cain
Nicholas Cain
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2084 Visits: 6200
BaldingLoopMan (2/24/2010)
mem settings
• If server memory is <= 3 GB, set min memory to 1 GB, and max memory to server less 512 MB.
• If server memory is > 3 GB, settings depend on the server platform (32-bit or 64-bit), presence of /3 GB in the boot.ini and on usage of AWE.
• For servers on 64-bit platform AWE is not required, and min memory should be server memory less 2 GB, max memory – server memory less 1 GB.
• On 32-bit platform with AWE : min memory and max memory should be server memory less 1 GB; without AWE – if /3 GB switch is not used, max memory = 2 GB, with the switch it is 3 GB (with min memory 1 GB less than that).


If you can I would leave at least 3GB for the OS in a 64bit system. Things like replication/connections/third party items all take up pieces of that memory space. I've run into quite a few issues as regards paging when not leaving plenty of room.



Shamless self promotion - read my blog http://sirsql.net
bobie
bobie
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 24
Yeah you should check the actual query plan.
One more thing maybe you should check the amount of IO or scanning actually happened using Set statistics io on then execute your query or sp.



ScottPletcher
ScottPletcher
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3946 Visits: 6686
Is the "MS Dynamics Navision ERP" application running on the same box as SQL Server in prod?

If so, I'd lower the fixed memory for SQL considerably.

Even if not, I'd still lower it to at least 96G (98304MB); at 128G, Windows itself needs some RAM to manage the other RAM.

The only non-memoty things that would normally ever slow it that much is:

1) I/O issues
2) tempdb issues.

So I suggest verifying those first before looking at other things.

SQL DBA,SQL Server MVP('07, '08, '09)

Prosecutor James Blackburn, in closing argument in the "Fatal Vision" murders trial: "If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them."
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47285 Visits: 44392
Please note: 3 year old thread


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


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