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
Store

DB Maintenance

I have recently found that my 2:15am database maintenance is taking a long time to run, anywhere from an hour

to over 4 hours. I am getting deadlock in the swdebugmaintenance log and i am loosing theses hours of data in

my DB when looking at historic data.

Just wondering how long others maintenance is running and if your getting the same deadlocks?

Find more posts tagged with

Accepted answers

All comments

FormerMember

I have the same problem running Orion NPM SLX 9.1, it can now take up to "4" hrs to complete the DB maintenance that kicks off at 2:15 AM and the graphical chart data is now totally missing during that time. We also are a 24 x 7 environment so that data is vital. Solarwinds team, what steps are being done to correct or is there something we can do to correct the problem?

FormerMember

We fixed a DB maintenance bug in SP1. Are you running SP1?

FormerMember

I will give SP1 for 9.1 a try, I had not yet installed that service pack thanks for the tip.

afsprau

I installed the SP1 for 9.1 and now the DB maintenance runs in 10 min, and no deadlocks.

thanks!

FormerMember

We fixed a DB maintenance bug in SP1. Are you running SP1?

I installed the NPM 9.1 SP1 last night, and checking this morning the graphical time gap was in fact greatly reduced (4 hrs down to about 10 minutes). Hopefully the next service pack will completely remove the overnight gap in data.

Thanks for the assistance,

Mark

FormerMember

SP2 won't do anything more in this area. If you'still re seeing gaps in your data during maintenance, it might be that you're database is stretched to its limits and the database maintenance "pushes it over the top" so that when the DB is being groomed, it's too busy to accept new data. That's the usual case when folks see gaps for DB maintenance.