3673681 - How to check the size of tables AL_HISTORY, AL_HISTORY_INFO and AL_STATISTICS - Data Services 4.x

The following performance issues may indicate oversized logging tables:

• Jobs running slower than expected
• Repository login times increasing progressively
• General system slowdown

Tables to Examine

Performance issues may be related to the size of logging tables that store job execution data. The following three critical tables should be examined:

• AL_HISTORY - Stores job-level execution statistics and Job Server information
• AL_HISTORY_INFO - Contains log file information
• AL_STATISTICS - Maintains execution statistics at the dataflow and transform level

Impact on System Performance

Over time, these logging tables can grow significantly as they accumulate data from every job execution. Large table sizes can impact:

• Query performance
• Repository response times
• Overall system performance

Data Services, performance, row size, AL_HISTORY, AL_HISTORY_INFO, AL_STATISTICS , KBA , EIM-DS-EXE , Job Execution , EIM-DS-SVR , Administration/Server , EIM-DS-CON , Connectivity , EIM-DS-DES , User Interface/Designer , How To