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!
- 1,074,405 hits
- RT @reza_rahman: What every responsible developer should know - "The Fallacies of Distributed Computing": rgoarchitects.com/Files/fallacie… 2 days ago
- Thanks @virtualJUG for having us tonight. Static or dynamic typing? Eclipse or IntelliJ or NetBeans? Answers here: buff.ly/15ZSnkP 3 days ago
Get Back in Control of Your SQL
Top Posts & Pages
- 10 Common Mistakes Java Developers Make when Writing SQL
- 10 Subtle Best Practices when Coding Java
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- The 10 Most Popular DB Engines (SQL and NoSQL)
- You Will Regret Applying Overloading with Lambdas!
- 10 More Common Mistakes Java Developers Make when Writing SQL
- Java 8 Friday: 10 Subtle Mistakes When Using the Streams API
- Java 8 Friday: No More Need for ORMs
- Java 8 Friday Goodies: Map Enhancements
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- You Will Regret Applying Overloading with Lambdas! January 29, 2015
- How to Translate SQL GROUP BY and Aggregations to Java 8 January 23, 2015
- jOOQ Newsletter: January 21, 2015 – Groovy and Open Source – jOOQ and the strong Swiss Franc January 21, 2015
- Open Source Doesn’t Need More Support. It Needs Better Business Models January 21, 2015
- Suis-je Groovy? No! What Pivotal’s Decision Means for Open Source Software January 19, 2015
- Using Java 8 to Prevent Excessively Wide Logs January 19, 2015
- Infinite Loops. Or: Anything that Can Possibly Go Wrong, Does. January 16, 2015
- Transform Your SQL Data into Charts Using jOOQ and JavaFX January 8, 2015
- How to Emulate the MEDIAN() Aggregate Function Using Inverse Distribution Functions January 6, 2015
- The Awesome PostgreSQL 9.4 / SQL:2003 FILTER Clause for Aggregate Functions December 30, 2014