Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > Implications of Last Database Sync and Last Database Update values

Implications of Last Database Sync and Last Database Update values

Table of contents
Created by Daniel Polaske, last modified by Tiarnan Stacke on Nov 03, 2017

Views: 416 Votes: 1 Revisions: 4

Overview

This article briefly describes the logic behind the Last Database Sync and Last Database Update values in the Polling Engines page within Orion Settings.

 

Environment

All versions of Orion products

Detail

  • Last database Update - this is the last time data was written to the database. Any time we write data to the database, this automatically resets.
  • Last database Sync - this is a routine/query that is executed from the dataprocessor service. It’s a long query but the summary of it is it updates the KeepAlive, element counts, and polling completion fields of the AllEngines table if any (node or interface or volume)WITH(NOLOCK) exists for the engine it is assigned to. The key is it is updating the element counts. The intent is to ensure that our Core Business Layer can communicate with the database.
     

These two values are exclusive of each other and updated differently. A comparison between the two will not yield any useful information as one checks to see if a specific service can talk to the database, the other is reporting that the database was updated. The database can easily be updated by another one of our services. The Database Sync is only 1 service (Core Business) that is updating specific fields. The value reported is the counter of the last time those fields were updated.

 

Troubleshooting will start differently because the values are updated in 2 different ways. However, because it could all come back to database it is possible that the same thing could cause both of those values to rise. There are many possible causes for both of those values to be vastly different from each other.

 

If one of the times is always a set period of time behind (For example, Last Database Update 5 minutes ago) then this is most likely caused by a time difference between the primary Orion Server and the SQL Server. To resolve this, align the time zones of the SQL Server and all Orion Server.

 

Last modified

Tags

Classifications

Public