If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Replicated MQTs REFRESH DEFERRED vs. REFRESH IMMEDIATE

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-27-05, 17:28
rubystep rubystep is offline
Registered User
 
Join Date: Sep 2003
Posts: 85
Replicated MQTs REFRESH DEFERRED vs. REFRESH IMMEDIATE

I have seen where despite the existence of a replicated MQT, the base table was being used when joined with a partitioned table due to the replicated MQT defined as REFRESH DEFERRED. Once it was recreated as REFRESH IMMEDIATE, REFRESHed and RUNSTATS run, it and not the base table was used for the join.
The key reason to having REFRESH DEFERRED is so it doesn't get populated every time a row gets inserted into the base table.
Is there a way to force the Optimizer to use the replicated MQT and yet having REFRESH DEFERRED?

Ruby

P.S. The reason that the Optimizer chose the base table was that with DEFERRED set it thinks that the base table has the most current data, and not the replicated MQT.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On