When I was reviewing a complicated SQL query with LEFT OUTER joins with 2+ million results,
I noticed that performance was critical. Normally with a few hundred queries, performance wouldn't be noticed.
Though because there were many LEFT OUTER joins, with so many results, the execution time would extend beyond 40mins+.
Normally, you would use the traditional UPDATE, SET, WHERE DML to update the Oracle SQL database, though how do you update
a SQL database using a a sub-query, which is referenced by the same Oracle table?
In this example, I've quickly highlighted the JMS (Java Message Service) components with a simple POJO (Plain Old Java Object) for
an asynchronous oracle database queue as well as constructing a JMS_TEXT_MESSAGE to the queue.
Often this issue occurs when you're trying to delete an old scheduled task or if you're performing an operation with a schedule
task that may otherwise should be working though obviously it doesn't.