 |
 |
Archives of the TeradataForum
Message Posted: Sun, 01 Jun 2003 @ 13:52:39 GMT
| Subj: | | Re: Cleaning up DBC tables |
| |
| From: | | Anomy Anom |
<-- Anonymously Posted: Sunday, June 01, 2003 08:14 -->
there are 12-14 tables in DBC that you can clean up. i use a crontab submitted set of sql . most all tables that can be cleaned up have
'thedate' as a column in them. i usually run sql that delete from dbc.ampusage where thedate lt date-90; try to run it during off hours as
it can cause some contention "slow down" of these tables being populated by normal usage of your system. if you question what tables are in
your system that you can clean up then run a space report at the table level for dbc. then wait 7-10 days and run it again. look to see
what tables have grown. look at these tables to determine what is in them, review the dictionary manual, and then start on your test
system. i have found that teradata will not let you delete from tables that it really needs. it will give you an error message. i run my
cron script once a week so there is always a rolling 90 days of information in these tables. if i am getting tight on overall space on the
system i might change the purge to 60 or 90 days. you can always check with your ncr fe for help in this area too.
| |
