ScottPletcher (9/16/2014)

---

I first look at SQL's usage stats (incl. row counts), operational stats and missing index info. Be aware they get reset when SQL stops and restarts, so you get a better feel if SQL has been up continuously for at least 30 days.

Also, look at wait stats and other performance metrics SQL maintains (unless someone has, yikes, turned some of them off for some reason -- if so, immediately re-enable them). As above, they are reset at restart.

Some of these are running totals, so you'll need to capture them at intervals (bihourly, hourly, half-hourly?, whatever) and then take differences to get a feel for the amount of activity during those time periods. You'll be able to see patterns of activity during the day as well.