Blog Post Series „How to tune ISV apps“

Inspired by Brent Ozars Blog post http://www.brentozar.com/archive/2014/12/whos-allowed-add-indexes-isv-apps/ I will start this series.

It will consist of:

  1. Capture the workload
    Capturing a typical workload during business hours.
  2. Diagnosis and Doing with “sp_BlitzIndex™”
    Diagnose and Delete/Alter/Add Indexes with the help of Brent Ozars “sp_BlitzIndex™”.
  3. Diagnosis and Doing with “Find Key Lookups in Cached Plans”
    Diagnose and Alter/Add Indexes with the help of Kendal van Dykes “Find Key Lookups in Cached Plans”.
  4. Setup Distributed Replay
    Setup a SQL Server Instance with Distributed Replay.
  5. Replay the workload
    Replay the captured workload against a backup first taken before capturing the first workload.
  6. Analysis of Performance Improvements
    Analyze two captured workloads with the help of Qure Analyzer.
  7. Analysis with Chrome Developer Tools.
    Load the ISV app in Chrome and make use of the Developer Tools to measure the response times of the Database Server.
  8. Subjective measurements
    Let human beings test the improved app.

Hope to keep you as readers,
Christoph Müller-Spengler

Advertisements
This entry was posted in SQL Server and tagged , , . Bookmark the permalink.

One Response to Blog Post Series „How to tune ISV apps“

  1. Pingback: How to tune ISV apps – Capture the workload | cms4j

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s