Archives of the TeradataForum
Message Posted: Thu, 25 Jul 2002 @ 07:32:40 GMT
David Clough wrote:
we experienced the same problem using UNION ALL some time ago.
We merged to tables into one bigger table, all having the same layout, like
INSERT INTO C
Table A had the size of 20 GB, Table B of 2 GB, so the target table (and the spool used) would be around 22 GB.
In fact, a spool of 80 GBs, i.e. four times more than the data to be copied, was used for this statement, and it took longer than expected. So far nobody from NCR could us explain why, but we think it's a bug. I think it's the same problem that occurs to you.
When we changed into a multi-statement, we got the right execution time and a used spool space of approx. 22 GB.
INSERT INTO C SELECT * FROM A
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|