Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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

SQL Log File Seems Excessive

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

Views: 839 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

Tags

Classifications

Public