http://msdn.microsoft.com/zh-cn/magazine/cc135978.aspx#S2
1.Identifying Logically Fragmented Indexes
2.Cost of Missing Indexes
3. Identifying Most Costly Unused Indexes
Examining this output it is possible to see how each index has been used by looking at the “user_…” columns. The “user_seeks” column identifies the number of times an index seek operation has been used to traverse this index to resolve a T-SQL statement.
The “user_scan” column identifies the number time an index scan operation has been used.
The “user_lookups” column identifies the number of times the index has been used in an index lookup operation . The “user_update” column to identifies how many times this index has been updated due to the table in which the index is associated has been updated by an UPDATE statement.
4. Identifying Most Costly Queries by I/O
5. Identifying Most Costly Queries by CPU
6. Identifying Queries Most Often Blocked
7. Find Longest Running Query
http://blog.sqlauthority.com/2009/01/23/sql-server-2008-2005-find-longest-running-query-tsql-part-2/