Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at email@example.com
This article explains what may be causing an issue where a transaction log file fills to capacity every 3 days.
The behavior seen is the SQL Transaction log fills to capacity every 3 days. This article only applies to Simple Recovery Model set for the Orion Database:
When full recovery model is set for SQL and the NTA installation is NTA 3.0 to NTA 3.11, NTA 4.0x86 (32bit server install) or 4.0.3x86 (32bit server install) due to NTA data compression tables will be truncated and shipped to other tables.
The flow of data goes as such:
Netflow_Detail tables > NetflowSummary1 >NetflowSummary2 > NetflowSummary3
Each time data is transferred from one table to another a transaction is written. The transaction can be quite large depending on the data being transferred. Each one of these data roll ups occurs at midnight, and all at once. This results in 3 different tables worth of data being averaged and redistributed to other tables all at the same time. This can quickly fill a transaction log if the recovery method is full.
Here is a better explanation of the compression and a break down of the data being transacted: