<jl*******@yahoo.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
creation is one time event and create-time recorded once in syscat. But
mod time could change from msec to msec on every table. I don't think
it is just impractical for db2 to maintain mod time for each table
object.
It is when you consider that you'd be doubling the number of updates you'd
have to do for every SQL -- you'd have the update on the table as per the
SQL statement (insert/update/delete), and then a corresponding update to the
proper data element in the catalogs.
Do you think that people who don't care about the last mod time to a table
should suffer the performance penalty?
The DB2 event monitor feature is a great way to track this information, so
if you want/need the last mod time for each table, configure and enable the
appropriate event monitor.
--
Matt Emmerton