Hello,

yes i made a mistake which shows indeed that samething is wrong in the execution plan.

I have forgotten to limit the data in T_AD_ACTUAL_DATE (Where condition).

But as you can see in the new Execution Plan although the data is now filtered (750 000 rows ) the optimizer does this filtering as last step.

On T server are 8 (big) processors, on Q are 16 (smaller) processors, but i think that should not influence the execution plan in this query.

Thanks again for your help!