Load Library Tracer Results - Database Structure

When you export the Load Library Tracer profiler results to a database, AQTime creates a number of tables in it. The contents of most of these tables correspond to the contents of AQTime panels in which the profiling results are displayed. This topic describes the structure of database table that contain the exported Performance profiler results.

The exported results are stored to the following tables:

The relationship between the mentioned tables is illustrated in the image below. This relationship is similar to the relationship of the data in AQTime’s Report and Details panels that contains the Load Library Tracer results.

Click the image to enlarge it.

The “root” table of the database is the INSTANCES table. It contains the list of all exported result sets and is shared by profilers. Each result set is identified by the INST_ID column value, which is unique among the table. All other database tables also have the INST_ID column that indicates the result set to which data of a specific table item belongs.

The LOAD_LIBRARY_TRACER_MODULES table corresponds to the result set that is displayed in the Report panel. Each row in this table corresponds to a module that was loaded to and unloaded from memory during the profiling. The ID column of the table specifies the modules’ identifier that is used by other database tables.

Each module that is listed in the Report panel could be loaded and unloaded several times. Every time the module is loaded, a module copy (or instance) is created in memory. The profiler traces the creation of module instances and displays information about them in the Module Instances table of the Details panels. The data of this table are exported to the LOAD_LIBRARY_TRACER_MODULE_INSTANCES database table.

Each record of this table corresponds to a module instance. The PARENT_ID column contains the module identifier (the same value that is stored in the ID column of the LOAD_LIBRARY_TRACER_MODULES table). The REC_ID column specifies the index of the instance relative to other instances of the same module. The ID column specifies the identifier of the instance in the table.

The profiler collects information about the sequence of function calls that led to the loading of a module in memory. The call stack data is exported to the LOAD_LIBRARY_TRACER_CALL_STACK table. Each row in this table corresponds to a function call. The PARENT_ID column specifies the identifier of the module instance, to which the call sequence corresponds (this is the same value that is stored in the ID column LOAD_LIBRARY_TRACER_MODULE_INSTANCES table). The COL__ column specifies the position of a call in the stack relative to other functions. The function call, whose COL__ is 0, corresponds to the top-most function in the call stack (that is, this is the call that loaded the module in memory).

The LOAD_LIBRARY_TRACER_CALL_STACK table has the REC_ID column that contains the identifier of the routine which corresponds to the call stack entry. Using this identifier you can retrieve information about the routine from the LOAD_LIBRARY_TRACER_META_ROUTINES table.

Below is detailed information about the tables.

The INSTANCES table

The LOAD_LIBRARY_TRACER_CALL_STACK table

The LOAD_LIBRARY_TRACER_META_ROUTINES table

The LOAD_LIBRARY_TRACER_MODULES table

The LOAD_LIBRARY_TRACER_MODULE_INSTANCES table

The RELATIONS table

See Also

Exporting Profiling Results to Database
Load Library Tracer - Overview
Load Library Tracer - Report Panel
Load Library Tracer - Details Panel
Using Actions
Using Triggers