Hi Carrie,
late reading but learning much, thank you for this article.
About multi-statement you said "any sub-expressions that the different SQL statements have in common will be executed once and the results shared among them (AMPs)".
How to consider the impact of a single execution and common result shared among AMPs in term of AWT consumption ? an always positive impact because of less work, a possible negative impact in some situations when a lot of AMPs are waiting for the results ?
Is there a guideline to evaluate the impact of a multistatement, as a 15 "select ... join from table1, table2 ... ;select ... join from table1, table2 ... ; ...." ?
Pierre
Hi Carrie,
late reading but learning much, thank you for this article.
About multi-statement you said "any sub-expressions that the different SQL statements have in common will be executed once and the results shared among them (AMPs)".
How to consider the impact of a single execution and common result shared among AMPs in term of AWT consumption ? an always positive impact because of less work, a possible negative impact in some situations when a lot of AMPs are waiting for the results ?
Is there a guideline to evaluate the impact of a multistatement, as a 15 "select ... join from table1, table2 ... ;select ... join from table1, table2 ... ; ...." ?
Pierre