How schema meta data impacts Oracle query transformations
I was recently wondering about some issue I had encountered between two tables. If tables undergo a lot of INSERT / UPDATE / DELETE statements, it may appear to be better to remove some constraints, at least temporarily for the loading of data. In this particular case, the foreign key relationship was permanently absent and I found the join between the two tables to be a potential source of bad query execution plans in greater contexts. So my intuition told me that this could be optimised by adding the constraint again, as Oracle would then be able to formally use that information for query transformations. I asked the question on Stack Overflow and it seems I was right:
But what does that mean? It’s simple. If you have two tables A and B, and you join them on A.ID = B.A_ID, having a foreign key constraint on B.A_ID may make all the difference. Let’s say, you execute this:
select B.* from B join A on A.ID = B.A_ID
Without a foreign key on B.A_ID
When B.A_ID is set (i.e. is not null), there is still no guarantee that there actually exists a corresponding A.ID. A is not part of the projection. Intuitively, it is thus not needed, but it cannot be optimised away, because the query will actually have to check for existing A.ID per B.A_ID.
With a foreign key constraint
When B.A_ID is set, then there must be a corresponding, unique A.ID. Hence, the JOIN can be ignored in this case. This has powerful implications on all sorts of transformation operations.
For more details, have a look at Tom Kyte’s presentation “Meta Data Matters”
That was awesome, right? Share it with your friends!
- 735,969 hits
- Want to detect dependencies that are no longer needed thanks to #Java8? Use Andrew Gaul's Modernizer Maven Plugin! buff.ly/XvwzZ3 3 hours ago
- Read @PeterLawrey's musings about #Java8 lambdas and side-effects. Would you have known these things? buff.ly/1r6iIEG 4 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- When the Java 8 Streams API is not Enough
- 10 Subtle Best Practices when Coding Java
- Why You Should NOT Implement Layered Architectures
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- The 10 Most Popular DB Engines (SQL and NoSQL)
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- 10 Common Mistakes Java Developers Make when Writing SQL
- This is the Final Discussion!
- 10 More Common Mistakes Java Developers Make when Writing SQL
- Top 10 Very Very VERY Important Topics to Discuss
- Top 10 Most Popular Articles on the jOOQ Blog September 22, 2014
- How Nashorn Impacts API Evolution on a New Level September 19, 2014
- This Just In!! Updated Silly Keyword Metrics September 17, 2014
- This is the Final Discussion! September 15, 2014
- Why You Should NOT Implement Layered Architectures September 12, 2014
- When the Java 8 Streams API is not Enough September 10, 2014
- Look no Further! The Final Answer to “Where to Put Generated Code?” September 8, 2014
- Stop Manually Importing Your ERD Export into jOOQ September 5, 2014
- Awesome SQL Trick: Constraints on Views September 2, 2014
- jOOQ Newsletter: September 02, 2014 – Do You Really Need Support? September 2, 2014