Archives of the TeradataForum
Message Posted: Tue, 15 Jan 2002 @ 16:20:02 GMT
I'd take out the collect statistics commands. In their current position they're telling the optimiser that the table is empty. When the problem query comes to run, the optimiser has stats which says that the tables are empty (i.e. the tables will be treated as very small). That will very possibly cause a 'less than optimal' (!) join plan. It's a good idea to use stats, I'd suggest that you collect stats for a table after you've populated the table.
I'd still like to see the explain.
Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|