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 Configuration Manager (NCM) > NCM Documentation > NCM 7.8 Administrator Guide > Configuration files > Automate config file purges

Automate config file purges

Table of contents
No headers
Created by Caroline Juszczak, last modified by Anthony.Rinaldi_ret on Oct 03, 2016

Views: 518 Votes: 1 Revisions: 4

If you do not need to keep historical configuration files and want to improve database performance, you can automate the removal of unnecessary configuration files. If your database is not stored on a high performance SQL Server, or is running on a locally installed instance of SQL Server Express, ensure you regularly purge unused config history.

  1. Click My Dashboards > Configs > Jobs.
  2. Click Create New Job.
  3. Name the job, and then select Purge Old Configs from Database from Job Type.
  4. Select the Schedule Type. If you are creating an Advanced schedule, use the five fields to create an appropriate cron expression.
  5. Add a comment if this job relates to a business rule, and click Next.
  6. Select the nodes to target with this job, and click Next.
  7. Select a Save option.
  8. Select an email notification option, and click Next. If you click Email Results, the default settings are populated. These settings can be overridden in each job.
  9. Select a Purge Configs option, and then click Next.
  10. Review the settings for the job, and click Finish.

 

Last modified

Tags

Classifications

Public