Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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,687 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