sem5_index.ndf and sem5_loginfo.ndf size increases

book

Article ID: 184708

calendar_today

Updated On:

Products

Endpoint Protection Data Loss Prevention Cloud Prevent for Microsoft Office 365

Issue/Introduction

The size of the two files is getting bigger and customers have to disable the size limitation on SQL database.

Cause

.ndf stores the operational transaction log for the database. If it grows fast, the database reads more frequently. This is controlled by the SQL server itself. Symantec can't control the speed of its growth. SEPM just calls the SQL interface to write the MDF file. ndf is the internal processing mechanism of SQL, and SEPM can't control it.

If you set a small upper limit, you may get a program exception due to the inability to write to the database when the upper limit is reached, such as a database process stop.

The method of dbcc and database compression is also the method provided by Microsoft sql server. Symantec does not directly operate on .ndf. It is not recommended to delete the records in .ndf directly.

 

 

Environment

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server 2016

Resolution

Customers are advised to use the following options:

1. Improve performance through SEPM settings:

  • Reduce the amount of logs stored in the database
  • Increase the DB maintenance
  • Remove old client packages
  • Reduce content revisions and removing unzipped packages


How to free up disk space on a Symantec Endpoint Protection Manager server
http://www.symantec.com/docs/TECH163063

 

2. If the above method is applied and there is no significant improvement, you can use the following workaround:

SQL 2005/2008 maintenance plan to shrink and limit the transaction logs of sem5 database

http://www.symantec.com/docs/TECH194305