×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
I can definitely see how running simple queries against a single table
(MQT) would perform better than having thousands of JOBS dynamically
"joining" 14 tables at runtime by "opening" a VIEW.
When you began this thread, I thought you were questioning the performance
of SQL VIEWS vs. embedding essentially identical SQL in HLL programs or SQL
stored procedures. That would be an apples to apples comparison. And I
suspect those comparisons would yield little if any difference in
performance.
Creating an MQT would save a lot of query processing associated with
dynamic joins at runtime. Seems like a good design.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
