Archives of the TeradataForum

Message Posted: Sun, 18 Apr 2004 @ 08:30:31 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I always go for option 3, not just for acclogtbl but for all system tables that collect data (resusage, eventlog etc.) There is no reason not to move the data elsewhere on a daily basis. This has a number of advantages

- Removes these skew issues

- Saves space as you can create the tables in non-fallback

- Removes system tables from the equation if performance issues are hit, if they are nearly empty all the time they won't be a problem

- Gives you one place to go to do usage/capacity analysis and you know you won't affect/be affected by true workload when doing this

The only downside is if you have tools that want to look at the DBC source. You can deal with this by changing the frequency you move data out of DBC.

Hope this helps

	<Prev	Next>		<<First	<Prev	Next>	Last>>