Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SQL Database maintenance and truncation best practice for Solarwinds ?

itengineer

Hi All,

What's the SQL Server database best practice that must be configured manually in the Solarwinds SQL Server?

Does the Transaction logs must or can be truncated manually every nightly backup considered safe or not?

Many thanks for considering my request.

Find more posts tagged with

Accepted answers

All comments

marcrobinson

Have you enabled the daily db maintenance job? This is setup in the web console - all settings - polling settings. Look for the Datase Settings. Check the Index Defragmentation option, leave most of the settings at default.The Archive Time is the when the DB maintenance program runs. You can check the logs on your server. Search for swdebugmaintenance.log on the primary poller. THat will give you a good idea of what was run, and completion. This does not entirely answer your question, but the db maintenance routine is a good first step.

itengineer

OK, from: https://prdsw-mon1.domain/Orion/Admin/PollingSettings.aspx just leave it as the default like below:

Seashore

Regarding transaction logs:
If you are running your db in "full recovery mode" you have to take log backups to truncate the logs. Depending on disk size and activity I suggest you take log backups every hour or so.

If you have the database in "simple recovery mode" (recommended by solarwinds (for some reason)) you don't have to bother about this.

itengineer

Can you confirm if the AL1100 license is used up entirely with no spare license, it could also corrupt the SQL database?

Seashore

No, using all licenses does not corrupt the database. What happens if there are no licenses left is that new components that are added does not work and gives an error stating that they are unlicensed. The licensed components still work.