You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Performance Issue After Joining EGO_ITEM_EFF_B on the basis of CHANGE_LINE_ID. Any solutions?

in Reporting & Analytics for Fusion Service

Hi,

I’m working on a query that previously ran within seconds, but after adding the lastLEFT JOIN, the execution time has increased significantly—even for a single change order, it now takes around 2 minutes. The purpose of the join is to retrieve the redlined value for a specific attribute tied to a particular change order, which is why I’m joining on CHANGE_LINE_ID. However, this addition has impacted performance quite a bit.

Could you help me understand why this join might be causing the slowdown, and suggest any optimization approaches? I need this query to run much faster for use in an automation process. Here is the code:

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!