asked
How to use page information in troubleshooting performance issues?
Please advise how we can use page information to troubleshoot the performance issues/or any other issues. What should we check/look in the page info to isolate the problems with page and what should we do to rectify it. Also, please provide few scenarios in which we need to look into the page.
I don't think you would typically start a troubleshooting session by looking at page information. That would come a bit later after you've been led to it via some other symptom like memory pressure or I/O issues Once you're down to the page level, you'll be looking at things like page density, fragmentation, and page splits Here is some good reading: - Data Page Count Influence on the Query Execution Plan: [
http://www.sqlskills.com/blogs/joe/data-page-count-influence-on-the-query-execution-plan/][1] - Row and Page Count Influence on Estimated CPU and I/O Cost: [
http://www.sqlskills.com/blogs/joe/exploring-row-and-page-count-impact-on-estimated-cpu-and-io-cost/][2] - Performance issues from wasted buffer pool memory: [
http://www.sqlskills.com/blogs/paul/performance-issues-from-wasted-buffer-pool-memory/][3] [1]:
http://www.sqlskills.com/blogs/joe/data-page-count-influence-on-the-query-execution-plan/ [2]:
http://www.sqlskills.com/blogs/joe/exploring-row-and-page-count-impact-on-estimated-cpu-and-io-cost/ [3]:
http://www.sqlskills.com/blogs/paul/performance-issues-from-wasted-buffer-pool-memory/
14 People are following this question.
