Archives of the TeradataForum
Message Posted: Fri, 16 Apr 2004 @ 15:28:43 GMT
<-- Anonymously Posted: Friday, April 16, 2004 11:26 -->
The DBC.AccLogTBL has a very high skew factor in our case - more than 85%. In fact, the smallest AMP has 1.5 MB of data, while the largest AMP has 55 MB of data.
I believe it is because a large chunk of our users logon once, and stay logged on for days on end, while they are submitting literally hundreds of SQL statements. The table has a PI on (logondate, logontime) columns. This is causing some of the AMPS in DBC to run out of space, even while overall DBC disk usage is fairly low. We cannot allocate any more space to DBC - already it is fairly large.
Any body else encountered this problem. If so, how did you work around it?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|