Don't forget about maintaining your SolarWinds Platform deployment

To maintain a healthy system, run the database maintenance regularly.

Database maintenance is an automatic process that optimizes the size of your SolarWinds Platform database. Database maintenance aggregates the data collected for a certain period and calculates new statistical values, based on the aggregated data. The detailed data is discarded, and only the aggregated statistics stay in the database.

Database maintenance runs every day at a specified time, by default at 2.15 am, and it should not take longer than two hours. Depending on the data granularity and retention period, you may need to configure your database differently.

The more granularity and the longer the retention period, the larger the database.

Specify when the maintenance runs

Make sure database maintenance runs after business hours.

1. Log in to the SolarWinds Platform Web Console using an administrator account.
2. Click Settings > All Settings.
3. Click Polling Settings in the Thresholds & Polling grouping.
4. Scroll down to Database Settings, and enter an Archive Time.

   

5. Click Submit.

Database maintenance runs every day at the specified time.

Run Database Maintenance manually

When in doubt, run the maintenance manually.

1. Start Database Maintenance in the SolarWinds Orion program folder.
2. Click Start.

Database maintenance runs immediately.

Find out how long the Database Maintenance takes

Database maintenance is a process that might affect the performance of your SolarWinds Platform deployment.

By default, your database maintenance starts at 2.15 am. For a healthy SQL server, it should run for 5 - 30 minutes.

If the database maintenance runs longer than two hours, investigate the tables with long maintenance times.

The database maintenance running longer than six hours or not completing at all indicates major issues in your deployment and results in performance issues.

1. Open the swdebugMaintenance.log at C:\ProgramData\Solarwinds\Logs\Orion\swdebugMaintenance.log.
2. Review the timestamp at the top to find out when the maintenance started.
3. Scroll down and review the timestamp when the maintenance finished, and calculate how long the maintenance took.
4. If the maintenance took more than two hours, skim the timestamps to investigate for which table the maintenance took long to complete.
5. When you have identified the table with issues, consider troubleshooting the elements that store data in the table.