Archives of the TeradataForum
Message Posted: Thu, 01 Mar 2001 @ 11:06:17 GMT
We have a 2 node 4700 box running V2R3 since January, 2001 and we're finding that using Volatile table's instead of the traditional temporary table's that the querries take up all the spool and if run concurrently with another querry will take alot longer to run. Is this the norm?
Also, does stats produce a different result if the table's index/columns have been defined with or without NOT NULL attribute.
Would the optimizer take a more agressive path if they were NOT NULL? and thus improve join efficiency/performance.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|