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 recovery model - Change recovery model to Simple

Database recovery model - Change recovery model to Simple

Table of contents
No headers

Updated May 5th, 2016


To view or change the recovery model of a database:

Why i should change DB recovery to SIMPLE instead of FULL ?

Open SQL Studio Manager. If SQL Studio Manager is not installed, download the installer from Microsoft.

  1. Edit the properties of the database.
  2. In the Select a Page pane, click Options, and choose Simple as the Recovery Model.

SolarWinds recommends that you use the Simple recovery model unless you have a SQL cluster.
If you have a SQL cluster set up for high availability (HA), you must use the Full recovery model. 


For example, Microsoft's Always On Availability requires a Full recovery model as seen in the article below.

Overview of Always On Availability Groups (SQL Server)

(© 2017 Microsoft, available at, obtained on February 13, 2017.)


If using Full Recovery mode the DB should be backed up every 30 minutes in order to stop the log growing to a problematic size. Large transactional logs can result in delays to alerts being displayed (alerts displayed after the trigger date) - With the SWIS Error: 'SolarWinds' is full due to 'LOG_BACKUP'


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified