Page History

Profiling provides the continuous monitoring of a data source and builds a statistical model based of database load based on the user's state every second. The created profile can then be saved to file, and the data can be saved, analyzed, and optimized by importing statements into the tuning component and running a tuning job.

The following list provides the general workflow and overhead tasks, when attempting to monitor data sources and store query information.

1. Execute a Profiling Session
2. Work with Session Results
3. Creating Profiling Reports
4. Saving Profiling Sessions
5. Import Statements to Tuning

In addition to the workflow tasks outlined above, the profiling interface also enables a number of important functions to help in statement analysis and diagnosis. This additional, or extra, functionality can be found in Other Profiling Commands.

Furthermore, in some cases you will need to configure system variables and parameters in order to get the results you need from the application. See Configuring DBMS Properties and Permissions for more information on how to configure profiling and your registered data sources prior to running a session.