Archives of the TeradataForum

Message Posted: Mon, 25 Feb 2002 @ 19:07:12 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

One thing about joining to the Calendar table in your problem - usually it is to qualify dates on some covered time period like Month, Quarter, etc. And you join on the date attributes. Consider a derived table to generate a one row, two attribute table that gives you the start and end dates of the period you are qualifying in your selection. That way the optimizer is more likely to copy that to all amps. It's something I picked up a little while ago and when I can use it I do. The plans are much better and I usually get that one row tables duplicated on all amps. See it that helps for your problem (if you can actually accomplish that).

	<Prev	Next>		<<First	<Prev	Next>	Last>>