 |
 |
Archives of the TeradataForum
Message Posted: Fri, 06 Dec 2002 @ 13:35:06 GMT
| Subj: | | Re: V2R5 Query Log vs Ambeo Usage Tracker |
| |
| From: | | Geoffrey Rommel |
| | I have been told by some that Query Log is not a tool to turn on and leave on. If that is true then how can I use this tool to get
historical data to do trending and uncovering dormant tables and columns? For example, I want to look back over a period of a year and find
all columns in our production tables that have not been used at anytime during that year. Is this possible with Query Log? | |
As I understand it, the Query Log will be like any other DBC log table (ResUsage, DBC.Acctg, etc.): there is no logic in the
database engine to delete rows from it, so it will just keep getting bigger unless you clear it out periodically. Many sites copy the data
from these tables to a historical database at least once a day and then clear out the logs. If you're not doing this already, you probably
want to start.
| |
