Hey Jeff, just a few answers (bold) while Sean's otherwise occupied:
1. Does it handle Partitioned Tables and Indexes without having to manually identify such things?
Currently it doesn't do anything special for partitions, but we're going to blow that out of the water in v.2 later this year.
2. Is there anywhere that you can see "why" an index was rebuilt? (As in what the frag level was).
Yes, we have extensive logging. The Minion.IndexMaintLogDetails specifically has FragLevel and PostFragLevel columns.
3. When in the ONLINE mode, does it automatically exclude (do OFFLINE) indexes with LOB involvement prior to 2014 or do you have to make an entry in the control table for that?
Online mode only does those that can be done online.
5. When it's doing a rebuild, does it take advantage of the BULK LOGGED Recovery Model for minimally logged index rebuild operations?
Minion gives you the option to switch to BULK or SIMPLE recovery before index maintenance, but we don't do it by default. That seems just a little presumptuous! To enable this for a database, set the RecoveryModel column in Minion.IndexSettingsDB. (This is covered in our online and in-product help.)
6. What's the SLA for support if something goes haywire? Does such support exist?
We don't have official support - it's a free product - but we wrote this to be a force for good in the world, so we pay attention to reports of "haywire" activity. Also bugs and irritations. Email, tweet, or submit a bug report on MidnightSQL.com/Minion. Or all three.
7. Does it do the optimization of rebuilding clustered indexes before it starts on the non-clustered indexes?
Not that I'm aware of, but we'll have to get Sean to answer authoritatively on this.
8. Since is does rebuilds, does it also automatically do the optimization of not rebuilding stats for indexes it just rebuilt?
Each maintenance operation (a single run of Minion Reindex, which may cover many fragmented indexes) is based off of a list of indexes that meet the criteria for rebuild or reorg. An index isn't hit twice in a single maint op, because Minion already checked it off of the to-do list, so to speak.
Keep em coming!