HistoryDB size got increased

Hi, 

Have you modified the default values for job history retention setting under Control Panel > Media Management > Data Aging. usually, the historyDB tends to grow if the default values have been changed to allow the job histories to be retained for a longer time, even though the data might have been pruned. 

You can also identify the table that has bloated under the Health Dashboard in Command Center, identify if you see any critical alerts for database. 

​@sbhatia 

I checked and found that the "FsNodeActivityData" table under HistoryDB is consuming a large amount of space.

Is there any troubleshooting we can perform to address or reduce the size issue?

That table is related to Anomaly Alerts generated by clients, if those Alerts are not acknowledge and acted upon, it may cause growth on the HistoryDB.

Are you getting more Anomaly Alerts than expected? Are those getting acknowledged?

Also, which FR is the CS running on? Does it have the latest MRs applied?

Interesting, I see one of our historydb’s have increased in size lately too. How do we check which table or what is the cause? None of the media management settings are any different than other CommCells and those DBs are 1/8th the size.

​@downhill you can use below SQL query to find which table is large in that DB.

 

USE HistoryDB;

SELECT 
    t.NAME AS TableName,
    p.rows AS RowCounts,
    SUM(a.total_pages) * 8 / 1024 / 1024 AS TotalSizeGB,
    SUM(a.used_pages) * 8 / 1024 / 1024 AS UsedSizeGB,
    (SUM(a.total_pages) - SUM(a.used_pages)) * 8 / 1024 / 1024 AS UnusedSizeGB
FROM 
    sys.tables t
INNER JOIN      
    sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN 
    sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN 
    sys.allocation_units a ON p.partition_id = a.container_id
GROUP BY 
    t.NAME, p.rows
ORDER BY 
    TotalSizeGB DESC;
 

Ah, I just noticed that it’s not the DB itself it’s the historyDB_log.ldf which has grown, and, I think it’s due to a ton more Salesforce objects and jobs. I suspect there’s no cleanup other than reducing retention under media management / aging is there? And probably don’t want to lose all that history anyhow. 30GB seems like a fair amount of logs though.