Accessing the Oracle Database
To many Java developers the Oracle database is simply a data store and can be left to get on with its work without interference. More traditional Oracle developers understand that the database is a sophisticated piece of software that offers a great deal of functionality, including an optimization engine that determines the path used to access your data. The optimizer’s task is to determine the possible access paths to the data and work out which access path will use the least resources. When we write our own code we can make sure that it is well designed and does not include anything that will adversely impact on the optimization of the statement. When we are using ADF it is important to understand that the SELECT statements in particular are being written for us, and therefore we need to understand the effect of some of the JDeveloper options that govern the writing of these statements.
This article considers the performance implications of the way we design our ADF applications. Note that it is focused on performance tuning of ADF applications from the perspective of the database, not on tuning the middle tier, which is a whole separate topics of its own. Get the paper here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog 
Twitter 
LinkedIn 
Forum 
Wiki
Developer Community 