Accelerate Hibernate and iBATIS applications using pureQuery, Part 3, Auto-tune data fetch strategies in Hibernate applications with pureQuery
From the developerWorks archives
Date archived: January 11, 2017 | First published: October 21, 2011
Development teams that build applications using Hibernate as the Object Relational Mapper (ORM), or persistence mechanism, spend significant time tuning the amount of data that Hibernate fetches from the database, and the number of SQL queries that Hibernate uses in each business use-case of the application. Database administrators have to deal with the database being slowed by SQL queries that join hundreds of tables, or thousands of SQL statements being issued in a single unit-of-work or transaction. These problems offset the productivity which was the reason for using Hibernate/ORM in the first place. In this article, learn how the IBM® InfoSphere® Optim® pureQuery auto-tuning feature for Hibernate automates the process of determining these problems and automatically fixing them without intervention. Both the application development team and DBAs benefit from the solution.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.