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!
- 673,414 hits
- "We've used @JavaOOQ and @Hibernate in really large enterprise projects, and they both perform exceptionally." buff.ly/1ltA4dT 3 hours ago
- "Why does jOOQ suggest to put generated code under “/target” and not under “/src”?" buff.ly/1x1LA5s 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
- 10 More Common Mistakes Java Developers Make when Writing SQL
- Stop Trying to Emulate SQL OFFSET Pagination with Your In-House DB Framework!
- 10 Subtle Best Practices when Coding Java
- 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
- Easy Mocking of Your Database
- Java 8 Friday Goodies: Map Enhancements
- Stop Unit Testing Database Code
- PL/SQL backtraces for debugging August 29, 2014
- Integrating jOOQ with PostgreSQL: Partitioning August 26, 2014
- All You Ever Need to Know About Recursive SQL August 18, 2014
- jOOQ Newsletter: August 15, 2014 – jOOQ 3.5 Outlook August 15, 2014
- A Wonderful SQL Feature: Quantified Comparison Predicates (ANY, ALL) August 14, 2014
- The Difference Between ROW_NUMBER(), RANK(), and DENSE_RANK() August 12, 2014
- The “Free”, “Standard”, “Open” Software Heresy August 11, 2014
- SQL Tip of the Day: Be Wary of SELECT COUNT(*) August 8, 2014
- Join the No OFFSET Movement! August 6, 2014
- Are You Using SQL PIVOT Yet? You Should! August 5, 2014