Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Database defragmentation option not enabled in Orion NPM by default

Database defragmentation option not enabled in Orion NPM by default

Table of contents
Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 1,887 Votes: 0 Revisions: 8


This article describes why the database defragmentation option is not enabled by default in NPM. Also, it describes the impact on having database defragmentation enabled.

This article is also part of Quick Orion database health check guide.


All Orion NPM versions


The DB fragmentation is normally performed by the SQL DBA by running DB Maintenance Tasks on a regular basis. This option is disabled by default in order to avoid duplicate tasks.

There are several tasks that should be performed on a regular basis. One of these tasks is to manage database fragmentation. Depending on the tables, queries, and indexes that are being used, fragmentation can cause performance issues, as well as using unnecessary space in the database.

Last modified