Archives of the TeradataForum

Message Posted: Wed, 21 Feb 2007 @ 13:17:28 GMT

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

Hmmm....it's quite interesting this - if the optimiser is re-ordering - as the version of the update code that gave you the 2663 works fine for me. No re-ordering necessary.

What are you running on?

It seems okay on: -

     RELEASE   V2R.06.01.00.52
     VERSION   06.01.00.58

Tried it with SQLA however, not BTEQ.

     Version   6.2.0
     ODBC      3.03.00.01

And I can't believe that it's entirely random.

Thoughts?

Mark Dodgson
CIO - Application Delivery - MI & Analytics Application Group - Engineering

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