Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Using WITH in SQL versus sub-query-which is better?

edited Feb 8, 2020 5:46AM in Reporting and Analytics for HCM 1 comment

Summary

Using WITH in SQL versus sub-query-which is better?

Content

Hi Experts,

Can someone help me understand if using WITH in SQL query really improve performance versus a sub-query or a scalar inline?
I don't really see why unnecessary you create a virtual table with tons of data when you will anyhow cut of ahlf of it using the following main query where you are probably going to use the WITH table in an INNERJOIN?
Isn't a tightly bound sub-query more faster?

Thanks,
Aloka

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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