well they only change if you analyze them, and that value could change even if you dont use it
Printable View
well they only change if you analyze them, and that value could change even if you dont use it
also what if you just update the table records..the number doesn't grow..but the table is still used.
The whole thing seems rather silly to me. Before we discuss it any further, I think the original poster should first prowide a very concise definition of what "tables that are not used" actualy means.
For me, a table on which an application merely performs SELECTs is no less used as the table in which application performs INSERTS/UPDATES/DELETES. And as allready said, if SELECTS on a table count as "table is used", then forget about triggers. In fact, forget about anything, except auditing. Audit trail is the only way to get that information from.
You can also collect and manage user-defined statistics for tables and domain indexes using thie DBMS_STATS package. ;)