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”
Everytime you read an excellent article and don't share it, god kills a kitten!
- 1,718,310 hits
- RT @bill_turner: Already like #jooq @kyleboon presenting at #gr8confus 4 hours ago
- RT @aaronzirbes: Learning #jooq from @kyleboon at @GR8ConfUS. Embrace SQL again. http://t.co/9AEp8cWOdI 4 hours ago
Get Back in Control of Your SQL
Top Posts & Pages
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- The Difference Between ROW_NUMBER(), RANK(), and DENSE_RANK()
- Do You Really Understand SQL's GROUP BY and HAVING clauses?
- Java 8 Friday: 10 Subtle Mistakes When Using the Streams API
- 10 Subtle Best Practices when Coding Java
- Java 8 Friday Goodies: Map Enhancements
- The 10 Most Popular DB Engines (SQL and NoSQL)
- 10 Common Mistakes Java Developers Make when Writing SQL
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- Top 10 Easy Performance Optimisations in Java
- Java 8’s Method References Put Further Restrictions on Overloading July 28, 2015
- NULL is Not The Billion Dollar Mistake. A Counter-Rant July 22, 2015
- What the sun.misc.Unsafe Misery Teaches Us July 20, 2015
- What’s Even Harder Than Dates and Timezones? Dates and Timezones in SQL / JDBC! June 30, 2015
- How to Debug Your Maven Build with Eclipse June 23, 2015
- Implementing Client-Side Row-Level Security with jOOQ June 17, 2015
- Querying Your Database from Millions of Fibers (Rather than Thousands of Threads) June 16, 2015
- JavaEE or Spring? Neither! We Call Out For a Fresh Competitor! June 10, 2015
- jOOQ Tuesdays: Axel Fontaine Predicts Exciting Times as our Industry is Maturing June 9, 2015
- What Exactly are SQL Views? June 2, 2015