Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated March 15th, 2016
Database Recovery Model - Changing Recovery Model to Simple
To view or change the recovery model of a database:
SQL Studio Manager
Open SQL Studio Manager. If SQL Studio Manager is not installed, download the installer from Microsoft® SQL Server® 2008 Management Studio Express (© 2017 Microsoft, available at https://www.microsoft.com/, obtained on February 13, 2016.).
Some customers prefer to have FULL Recovery ,usually as their main concerns are because they most likely have mirroring on their Orion DB and they do not wish to turn off full Recovery.
Mirroring can be done with Log shipping, DB Snapshots or 3rd Party software. But this is up to Customer to implement.
As SQL Server is 3rd Party, SQL Server support is limited on that, so please consult with your DBA. NPM Customers do not usually need High Availability\Protection Recovery for a product like NPM, whereas High Performance is critical. So where possible we recommend to change recovery to SIMPLE Mode where possible and also see our Disaster Recovery documents.
Having a FULL recovery Model causing a lot of overhead to give such redundancy and with WRITE Intensive DB like Orion NPM and especially with Netflow that could cause LDF File to bottleneck and grow out of Control. SIMPLE recovery is not as intensive and can handle to intensive writes to it.
The transaction log should be sized based on the amount of data modifications made to a database and the frequency of the log backups. Large data modifications, such as data loads or index rebuilds should be taken into account when calculating a log file size.
Also remember that in order to stop Transaction LOG from growing excessively, backup frequently when in Full Recovery. Working with Transaction Log Backups / (© 2017 Microsoft, available at https://msdn.microsoft.com/, obtained on February 13th, 2017). “More frequent log backups have the added advantage of increasing the frequency of log truncation, resulting in smaller log files.”
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.