With the WITH OBJECTS option, DBQL logs one row in DBQLObjTbl and the associated view, QryLogObjects[V], for each data object referenced by the query. An object can be a database, data table, column, secondary index, join index, or journal table. (If the object is a secondary index, its number is logged rather than a name.) DBQL gets the use counts from the Optimizer and not the SQL statement itself. The system logs a count of the number of times the Optimizer accessed the object.
The following table lists the fields populated in the object log view.
|CollectTimeStamp||Time that the rows were written to the database.
For more information on CollectTimeStamp, see Comparing CollectTimeStamp Value Between Tables.
|FreqofUse||Number of times the object was accessed, as determined by the Optimizer, to process the query.|
|ObjectColumnName||Name of the column. Or if the ObjectType is 'Idx' or Index, this field returns the name of the column associated with the index.
Some queries will not provide a name, such as COLLECT STATISTICS.
For multicolumn indexes, there will be one additional row for each column in the index and each row will have the same object number.
|ObjectDatabaseName||Name of the database that owns the target object.|
|ObjectID||Unique internal identifier of this object.|
|ObjectNum||Number of the column or secondary index.|
|ObjectTableName||Name of the table or view.|
|ObjectType||Character code indicating the type of object targeted.
For the possible values for this column, see ObjectType Column Values
|ProcID||Unique processor ID of the Dispatcher and part of the multi-column NUPI (see also CollectTimeStamp).|
|QueryID||Internally generated identifier of the query.|
|TypeOfUse||Describes the use of the object. TypeOfUse contains the following numerical values:
More than one of these values can be used.