.. The problem is that for many of us, we may run DBCC CHECKDB on another machine, perhaps on a restored copy of production, so how can we track this? ..
The default trace logs DBCC CHECKDB events.
It does, true, but the question raised in the article is, if you run CHECKDB against a copy, how does someone else know you ran it against that DB if they're checking production? How do you somehow transfer the results from the copy to production?
If you're on SQL2016 SP1, you can't update the property (DatabasePropertyEx() -> LastGoodCheckDbTime) so how would you do it?
I don't see the point in transferring results. The online database and the restored copy are two different instances. Just because one is checks out ok, the other could still be bad.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho