SQL Server Performance Tuning

ABOUT ME

Aditya BadramrajuTwitter:http://twitter.com/@aditya_feb22Blog:http://adityabadramraju.wordpress.com

Agenda SQL Server Performance Tuning Overview CPU Input/output Memory Conclusion

Slow Performance !!!U DBA!!I want

application run in rocket speed

So How Do I Do

Monitor

Troubleshoot/

Get the Victim

Tune Test

Implement

Monitoring

Analyze

Collect

Compare

Identify

Measure

Dig in to details

Troubleshoot/Get the victim

TuneCorrect it!

Optimize it!

Change your

approach

Test and Implement

Get the victim!!The victim for performance majorly lies in any of

these areasCPUIOMemoryTemp DB Bottle NecksPoor Indexing ,query writing and maintenance

CPUCheck the Task ManagerCheck Perfmon CountersIf SQL Server is responsible for high CPU find

the session which is consuming the CPUDig in to details of the sessionsFind the CPU costing queries If the environment is OLTP beware of

MAXDOP

IODMV sys.dm_os_wait_stats is the best thing

which says you are at IO crunchPerfmon counters such as Diskreads/Sec,

Diskwrites/Sec, IO queue also gives clear picture in this front.

When you found IO as culpritSpread the data into different drivesCheck the queries which costs high Logical IOCheck for DISK Defragmentation and Index

Fragmentation

MemoryWe can get the very first glance of it through

Task ManagerPerfmon Counters like Page Life Expectancy,

Buffer Cache Hit Ratio, Memory Grants Pending, Free Pages

Page file configuration on the serverAdhoc QueriesPoor Query WritingIncorrect Memory SettingsLock of Memory Pages in 32 Bit System.

TEMPDB Bottle NecksIts used more than What we normally thinkIt is responsible for all Sorts, Hashes, DBCC,

Index Rebuilds and more.The bottle necks of TEMPDB are due to

Incorrect tempdb configurationIncorrect usage of temporary variablesUnnecessary Sorts on major tables etc.

Poor Indexing and maintenance

The above said problems are inter related and basic problems will bePoor Query writing like using joins(Not

appropriately of course ),Cursors, triggers etc.

Having huge index fragmentation and huge page density

No update for statisticsAnd lastly not having a Dedicated DBA

(ATLAST I HAVE SAID THAT )!!!!

AcknowledgementsPaul Randal –SQL SKILLSAdam Machanic-MicrosoftSQL Server Internals by KalenPinal Dave –SQL AuthoritySQL PASS and all SQL Organizations

LAST WORDI like to MAD

and U???

……