dclark,
We have a primary and secondary table relationship which instead of being a one to one or a one to many relationship, it is a one to one based on condition.
Most analyst/developers can get the first requirement, but miss the conditional portion.
This logic can easily defined and hidden from the average user by defining the logic within a DB2 View and have them reference the DB2 View.
On Fri, May 13, 2016 at 2:41 PM -0700, "dlclark@xxxxxxxxxxxxxxxx" <dlclark@xxxxxxxxxxxxxxxx<mailto:dlclark@xxxxxxxxxxxxxxxx>> wrote:
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/13/2016
05:10:17 PM:
I think the idea is that if you need a given SQL statement, the
performance hit is there regardless of rather or not it's in a view.
We don't disagree with that. The paradigm shift for us was not a
simple choice between embedding an SQL statement in a program or embedding
it in a view -- though we were given the impression that the same
statement would perform a bit better in a view. Rather, it was mostly
about coming face-to-face with the realization that the view is rendered
at run time as opposed to a DDS-based LF which is rendered at object
creation time. Thus, a particular case that came out of the performance
review was that we had to change a particular view to an MQT in order to
render the many hundreds of thousand of rows of data from a 14-way join
just once per day (in a separate process) rather than 10,000+ times per
day in the middle of user's interactive jobs.
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.
*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
