- Learn to differentiate IO Issue, CPU Issue, Network Issue
- IO Issue - Excessive IO can be due to a SCAN on a big table. There are ways to convert SCAN to SEEK. In a OLTP system query are expected to be highly selective, fetch few records
- CPU Issue - During processing we might have temp tables, Sort a Temp tables. Sort Operator is usually CPU intensive. Wait Stats sys.dm_os_wait_stats DMV provides more info. Please check Joe Sack wait stats link mentioned below
- Disk Issue - PhysicalDisk/LogicalDisk counter in below bookmarked excel and values defined for it for interpreting Disk Issues
- Network Latency - Network Interface counter in below excel provides values for counters and interpreting them
List of Counters and Optimal values for them
Without writing any query how do we find expensive queries
- Activity monitor check recently expensive queries
- Goto Particular Database that you want to check. List Reports for Reports->Standard Reports->Top Transactions by Age, Locks
- Check Parallelism Enabled/Not Link
- Best Practices for Troubleshooting Slow Running Queries
- Q&A: Performance Tuning Redefined with SQL Server 2008
- Are you using SQL's Missing Index DMVs?
- Top SQL Server 2005 Performance Issues for OLTP Applications
- SQL Server: 4-Step Performance Troubleshooting Methodology--Introduction
- Wait Stats by Joe Sack
- Who is Active? v9.57: Fast, Comprehensive DMV Collection - What's Really Happening on Your Server?
- Drum Roll, Please...The Debut of The SQL DMV All-Stars Dream Team!
- Top 8 Queries to Improve DB Design
- SQL Performance Optimization
- The SQL Server Wait Type Repository… - Very Good
- SQL Server I/O Bottleneck, I don't have one, YES YOU DO!
- SQL Server Performance Tools - Boise Code Camp Presentation
- Performance Counters Analysis : SQL Server , IIS , MOSS , BizTalk , Exchange , and Active Directory
Happy Learning!!!
No comments:
Post a Comment