|
Archives of the TeradataForumMessage Posted: Tue, 23 Sep 2003 @ 00:01:49 GMT
Julie, Check the logic of your MSR's that are not working 'properly'. Specifically check that they logically can be run as part of an MSR. For instance the following request cannot be logically run as an MSR: Insert into t1 select ....... from t2 where.... ;insert into t1 select..... from t2 where xxx not in (select ..... from t1 where ...); This is because the first statement must complete before the second statement can start (because the second statement uses the contents of the target table in the first statement - i.e. it uses the results of the first statement) This second example can logically run as an MSR (because the 2nd statement doesn't require the 1st to complete): Insert into t1 select ....... from t2 where.... ;insert into t1 select..... from t2 where xxx not in (select ..... from t3 where ...); A long time ago (and I mean a long time) there was a bug whereby the first example above would have been optimised as an MSR (but it shouldn't have). What you may be seeing is that having done the upgrade, you now have the fix for that bug and these requests are now (correctly) not being run as an MSR. If that's the case, then to fix your problem about checking for ActivityCount, you need to break those requests apart to smaller MSR's or single statement requests and take appropriate action on each one. Cheers, Dave
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||