Archives of the TeradataForum
Message Posted: Tue, 24 Jan 2012 @ 16:10:38 GMT
it has probably something to do with data blocks. Some guru might be able to explain it in more details.
Try to make your table multiset with a NUPI and insert the same value ('ABC' for example) a few times. You will see that the size of the table does not change at first few shots. The fact that your table grows 512 bytes each time you insert a value is that you happen to insert a unique value that is hashed to a "new AMP". Once your table will be populated with some reasonable number of rows, the growth will be much more predictable.
Also, try not to sum the currentperm, but list it by vproc for a better visibility.
Finally - it is not recommended to use dbc.AllSpace for table size. Use dbc.TableSize instead.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|