dalfanz
Well Known Member
List:
It appears the Business views are dynamically joined so when each applicable
sequel request is done, it goes out and have to join the file for each of
these sequel request.
This requirement seems much more system intensive/slower than desired for a
general fetch especially against non-joined views. Is there a potential way
to have these joins already built, thereby increasing performance?
Can we create these joins under what for application is looking for? Or can
the JDE tool set
not recognize these?
Or is this handled effeciently "under-the-covers" enough and its more of the
application having other filters to look at that the other non-joined
application is not required to look?
Curious.
It appears the Business views are dynamically joined so when each applicable
sequel request is done, it goes out and have to join the file for each of
these sequel request.
This requirement seems much more system intensive/slower than desired for a
general fetch especially against non-joined views. Is there a potential way
to have these joins already built, thereby increasing performance?
Can we create these joins under what for application is looking for? Or can
the JDE tool set
not recognize these?
Or is this handled effeciently "under-the-covers" enough and its more of the
application having other filters to look at that the other non-joined
application is not required to look?
Curious.