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”
- 226,718 hits
- RT @bozhobg: jOOQ looks like a nice library for writing type-safe SQL #java2days 1 day ago
- RT @mookid8000: sounds like Ceylon's sequence features are pretty neat: blog.jooq.org/2013/12/03/top… (favorite no. 2 on the list) 1 day ago
Get Back in Control of Your SQL
Top Posts & Pages
- Top 10 Ceylon Language Features I Wish We Had In Java
- 10 Subtle Best Practices when Coding Java
- The Java Fluent API Designer Crash Course
- SQL Trick: row_number() is to SELECT what dense_rank() is to SELECT DISTINCT
- Top 10 Lists of Common Java Mistakes (That Makes Top 100!)
- The Open Source Bikeshed.
- Does Java 8 Still Need LINQ? Or is it Better than LINQ?
- 10 Common Mistakes Java Developers Make when Writing SQL
- ElSql, a new external SQL DSL for Java
- On Java 8's introduction of Optional
- When Source Code Comments Indicate Trouble December 4, 2013
- Top 10 Ceylon Language Features I Wish We Had In Java December 3, 2013
- The Jodd SQL Generator December 2, 2013
- The Open Source Bikeshed. December 1, 2013
- jOOQ Newsletter November 29, 2013 November 29, 2013
- Evil Field Injection vs. Annotatiomania™ with Lombok November 29, 2013
- Detect JDBC API Misusage with JDBCLint November 28, 2013
- Using jOOQ with JAX-RS to Build a Simple License Server November 27, 2013
- A Lesser-Known Java 8 Feature: Generalized Target-Type Inference November 25, 2013