Archives of the TeradataForum
Message Posted: Wed, 21 Jul 1999 @ 22:13:14 GMT
thanks for those suggestions. I'm glad someone explained the benefits of MLOAD delete over normal BTEQ's for me.
Regarding 'optimised V2R3 BTEQ deletes'. Will it still benefit from the dropping of secondary indices prior to any deletes? We currently drop all secondary indices which gives us a performance benefit which outweighs the overhead of recreating the indices later.
FYI: the error WAS reproduced in the test environment as I was initially mis-informed. However, it was converted, more sensibly, to import a single record date parameter for a MLOAD DELETE task.
38m rows were deleted in just over an hour. I don't have the luxury of 48 nodes a 5150 or V2R3 but that wasn't bad really!
One thing I couldn't quite follow was why insert/select 500m - 6m = 494m rows into another table? That's rather less than 25% as mentioned.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|