Submit a ticketCall us
Home > Success Center > Netflow Traffic Analyzer (NTA) > SQL Transaction Log Filling every 3 days

SQL Transaction Log Filling every 3 days

Table of contents
Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 22 Votes: 0 Revisions: 5

Overview

 

This article explains what may be causing an issue where a transaction log file fills to capacity every 3 days.

Environment

  • NTA versions 3.0 - 3.11
  • NTA 4.0x86 (32bit server install) - 4.0.3x86  (32bit server install)

Detail

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:

https://msdn.microsoft.com/en-us/lib.../ms189275.aspx

 

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:

https://solarwinds-prod.mindtouch.us...nd_compression

 

 

 

Last modified
20:59, 22 Jun 2016

Tags

Classifications

Public