Fully and minimally logged

Reports on “Fully Logged”, for fully logged operations, and “Minimally Logged,” for minimally logged operations. Occasionally items are in the "Fully Logged" subsection but not in the “Minimally Logged” because the item is not applicable to minimal logging.


APL Heap Tables

Number of row inserts that took place on allpages-locked heap tables—all tables that do not have a clustered index. This includes:

The “% of total” column shows the percentage of row inserts into heap tables as a percentage of the total number of inserts.

If there are a large number of inserts to heap tables, determine if these inserts are generating contention.

Check the sp_sysmon report for data on last page locks on heaps in “Lock Detail”. If there appears to be a contention problem, you can query the monitoring tables to determine which tables are involved.

In many cases, creating a clustered index that randomizes insert activity solves the performance problems for heaps. In other cases, you might need to establish partitions on an unpartitioned table or increase the number of partitions on a partitioned table.


APL Clustered Table

Number of row inserts to allpages-locked tables with clustered indexes. The “% of total” column shows the percentage of row inserts to tables with clustered indexes as a percentage of the total number of rows inserted.

Inserts into allpages-locked clustered tables can lead to page splitting.

Adaptive Server may use worktables with clustered indexes to perform vector aggregates (for example, group by), although a hash-based algorithm is more common for Adaptive Server release 15.0 and later.

See “RID Upd from Clust Split” and “Page Splits”.


Data Only Lock Table

Number of inserts for all data-only-locked tables. The “% of total” column shows the percentage of inserts to data-only-locked tables as a percentage of all inserts.


Fast Bulk Insert

Number of inserts by a partially-logged fast bcp.