sql - Why won't DB2 use my MQT table? -


I have created a user named MQT (physical content table) in DB 29.7 (1 has not been set yet ). This main fact is a simple set of tables

  • MQ was built with search optimization enabled and created by user attributes

    Li>

  • Refresh defrade and Amp; Initial data (maybe I should not be?)
  • Setting Registry Variables, using DQ2 to use all types of MQTs for optimization
  • "Set to Texx Flip the cache: flush package package cache dynamic
  • Make sure that the default query optimization class is at least 2 levels.
  • Run the runstats. Was (this is at 5)
  • Set the default refresh age to 0 (though I think it does not matter to user-defined MQTs)

Then it was tried to determine whether the adapter MQT will use:

  • I have tried that the various simple questions are called MQT - either:
    • SELECT COUNT (*) FROM fact_table
    • or Select group-dimension, COUNT (*) FROM group-dimension by fact_table GROUP.
    • Explain (using db2expln) only the fact table is referenced and not MCT
    • The query results show that the fact table and not the MTT table
    • the question period fact The table was compatible with and not the MCT table.

    Anyone will either suggest a simple method whether a query is using an MCT or should I try it before using it?

    2 things:

    1) What's that? Tunnel types have been preserved for existing set to register? This is the DFT_MTTB_TYPES database configuration parameter - and the default value is 'system', so this adapter will ignore your MQT.

    2) In addition, your assumption DFT_REFRESH_AGE and MQTs created by the user are incorrect. For the MQT maintaining user, the current refresh age register should be set for any refresh so that the proposed MCT can be refreshed.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -