View Single Post

   
  #10 (permalink)  
Old 07-01-2008, 08:08 AM
peter
 
Posts: n/a
Default Re: When does a stored procedure use an MQT

On Jun 30, 9:37*pm, Serge Rielau <srie...@ca.ibm.com> wrote:
> *>None show the merge command yet show the update and
> *>insert statements.
> Please clarify "show".
> Do you mean the optimizer plan?
> If so then yes, that makes sense. The DB2 compiler breaks MERGE down
> into its individual components.
> Typically you see an outer join between source and target, followed by a
> join with a UNION ALL with UPDATE/DELETE/INSERT operations stacked on
> top as requested.
> This behavior is not special for MERGE however. It is normal for the
> compiler to break statements down (or add to them).
>
> Cheers
> Serge
> --
> Serge Rielau
> DB2 Solutions Development
> IBM Toronto Lab


Not talking about the optimizer plan, talking about the statements
that form the DBRM which is stored in the system tables which can be
shown by the "show explainable statements" option on the package list
menu. They do not exist in the DBRM even in broken down form from
what I have seen.
Reply With Quote