Archives of the TeradataForum

Message Posted: Mon, 22 Sep 2003 @ 15:41:31 GMT

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

Hi,

We have noticed a change in the way some of our multi-statement requres are behaving and wonder if anyone can explain it. (We recently upgraded from V2R3 to V2R4.1 and have noticed the change since then).

Previously, if we did a number of Insert/Select statements using an MSR, the job output did not show the no. of rows inserted by each part of the MSR, but displayed one overall total at the end (Bteq scripts). Now however, for certain jobs (not for all), we see a breakdown of the no. of rows inserted by each part of the MSR. (And can see from the Explains that a number of merges are being done into the target table).

Initially, we found this was very useful, however, it is causing problems, as we use Activitycount checks to ensure rows were inserted by the MSR - and if the LAST part of the request returns no rows, the activitycount appears to be zero, regardless of whether the other parts returned rows.

Can anyone explain this change to us, and shed light on what instances more than one merge will be done??

Thanks, Julie.

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