"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/13/2016
07:10:44 PM:
BTW could your problem with the wrong data be an not updated/refreshed
MQTs.
No. We only have just the one MQT at this time and it is shared
(it is not replicated in other libraries). So, we now use static SQL to
access it. I understand that ideally an MQT should only be built once and
permanently. But, in this case, the underlying data does change
occasionally and thus this MQT must be refreshed occasionally. The
performance issue came up because the original view was being re-rendered
too many times per day (in the tens of thousands). Changing it to an MQT
cut this down to being rebuilt at most once per day. A definite
improvement.
Sincerely,
Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
As an Amazon Associate we earn from qualifying purchases.