Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > SQL Log File Seems Excessive

SQL Log File Seems Excessive

Created by Mindy.Kerber, last modified by MindTouch on Jun 23, 2016

Views: 11 Votes: 1 Revisions: 2

Overview

Customer runs a full SQL backup with 100 GB of space set aside for the log files but customer cannot acquire any more space for the log files after backup because 93 GB were taken immediately from 100 GB log files space. 

Environment

  • NPM releases

Cause 

Customer was unable to perform a full backup and compression of the log database.

Resolution

The following are solutions to acquire more space for the log files:

  1. Setup a maintenance plan to run a full back up every night.
  2. Compression of log database.

 

 

 

Last modified
23:39, 22 Jun 2016

Tags

Classifications

Public