I thought most people just use DMVs to find most expensive queries for tuning
Well, in this case, I'm not exactly trying to find the most expensive queries - I've already done an analysis of the reporting, and I know which reports are the big ones. There are a dozen or so big reports that run over the weekend so they're ready on Monday morning, and they touch dozens of tables across the database. What I want to do at this point is have the system figure out which tables are being hit the most, and in what ways, so I can create some appropriate indexes to speed things up.
Robert, thanks for the response.
I'll probably update this on Monday or Tuesday and let everyone know how it goes.
