TVM and Dbase are both tables that commonly have stats collected on them. So I don't see a problem with collecting stats in addition to the ones usually recommended for those tables, if you see an advantage of doing so. Adding new stats to DBC tables doesn't really have a downside and usually they are very quick to collect (usually Dbase and TVM aren't terribly large). They will be ignored by the optimizer if the optimizer does not need them for a particular optimization, so there's no extra overhead there.
The best approach is to try out the stats collections and see if they give you better plans for this macro. That is always the best way to determine if a certain statistic is going to add value or not. See if you get a better plan and a faster query.
TVM and Dbase are both tables that commonly have stats collected on them. So I don't see a problem with collecting stats in addition to the ones usually recommended for those tables, if you see an advantage of doing so. Adding new stats to DBC tables doesn't really have a downside and usually they are very quick to collect (usually Dbase and TVM aren't terribly large). They will be ignored by the optimizer if the optimizer does not need them for a particular optimization, so there's no extra overhead there.
The best approach is to try out the stats collections and see if they give you better plans for this macro. That is always the best way to determine if a certain statistic is going to add value or not. See if you get a better plan and a faster query.
Thanks, -Carrie