I'm considering asking our DBA's to disable their weekly SQL maintenance routines. Periodically, we seem to run into an issue where SolarWinds' inherent maintenance job will collide with our in-house maintenance jobs.
Is SolarWinds' recommendation that only their maintenance routines be run? Or could their be critical things in a SQL maintenance routine that we should keep running in tandem?
You can always change the time the Orion DB maintenance runs so it does not collide with your other jobs. The link below describes how you can edit that setting.
I had thought there was a substantial enough timing offset already in place but for whatever reason another collision occurred recently.
I just figured that if there was no point in having our DBAs run theirs, I would ask them to skip it...
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.