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


Most common types of fix...


Most common types of fix...

Author
Message
Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
Hi all, I've been taking a look around the Perf fora recently and comparing the scenarios to my own findings, and I was curious as to which types of solution you all have found are the most prevalent.

I'd say the following types of fix are most common, so imo, in descending order;

1) Code rewrite;
2) Memory/CPU upgrade;
3) SQL Server reconfiguration;
4) Disk System upgrade/reconfiguration
5) OS reconfiguration
6) Server/Service restart

Like I said, I'm curious to know if this agrees with (or how this differs from) your own experiences.
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: 47396 Visits: 44399
1) SQL code changes
2) Indexes
3) Application code changes
4) Database config changes
5) Hardware upgrades (IO predominately, very hard to max out a modern CPU with well-written code)

Restarting SQL is not a performance fix. If restarting SQL improves performance then there's some config or code problem that needs to be identified and resolved.


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


Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
GilaMonster (3/19/2012)
1) SQL code changes
2) Indexes
3) Application code changes
4) Database config changes
5) Hardware upgrades (IO predominately, very hard to max out a modern CPU with well-written code)

Restarting SQL is not a performance fix. If restarting SQL improves performance then there's some config or code problem that needs to be identified and resolved.


Agree completely that restarting SQL is a quick and even dirtier method of brushing problems under the rug, and with #5 not including CPU, to be honest I hesitated in mentioning either.

I'm surprised at # 4 however, what database-level changes have you found most involved with improving performance?
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: 47396 Visits: 44399
Jake Shelton (3/19/2012)
I'm surprised at # 4 however, what database-level changes have you found most involved with improving performance?


AWE on 32 bit instances (instance not database level), max server memory (instance not database level), forced parameterisation, optimise for ad-hoc workloads (instance not database level), snapshot or read committed snapshot. Turning off autoclose/autoshrink, fixing growth increments, fixing log fragmentation.

Huge gap between 3 and 4 though, and most of those are not for SQL 2000


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