Archives of the TeradataForum

Message Posted: Tue, 03 Aug 2010 @ 17:35:00 GMT

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

Ah, yes. That is another thing it will do at that time. If you have a large number of History rows that option will cause it to take a long time. (It has to read every history row and compare it with the current query.)

For relatively small History files that is generally a good option to use - it prevents the History from getting too large.

Applying a History Filter will improve startup time, but it has no effect on the size of the History file or on the performance of any of the History functions.

Since some users now have History files of 300MB plus we will be adding a new 'History cleanup' function in a future release. This will allow you to specify a set of criteria (similar to the History Filter) for rows to be deleted.

In addition it will allow you to request an overall duplicate deletion - that will be slow, but should only be required occasionally.

Mike Dempsey

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