Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Changes in the Alertlog table in NPM 11.5.2 version

Changes in the Alertlog table in NPM 11.5.2 version

Table of contents

Updated March 11th, 2016


This article explains some of the Alert Table changes in NPM version 11.5.2  from the previous versions.


NPM version 11.5.2


There are major architectural changes in the database tables with the newest version of NPM. The Alertlog table is no longer valid for 11.5. The following are the newest tables that are included in the new structuring:



  • AlertConditionState - used by the service for evaluated alert conditions.
  • AlertActive - contains currently active alerts. When an alert is triggered, then a new record is created for a given object. When an alert is reset, then a record is deleted for the given object.
  • AlertObjects - when active alert is triggered and for triggered swis entity does not exist, a record is added. When alert is reset, the record is not deleted. Deleting orphaned record takes care of database maintenance.
  • AlertActiveObjects - used for global alerts (one alert is triggered when more objects fulfill trigger condition). It contains a list of objects that trigger the alert.
  • AlertHistory table - storage of every action completed with active alert such as trigger, reset, acknowledge, added note, and action execution.


If you are looking for what the old table AlertLog has changed to, then the table that you are looking for in the newest version of NPM 11.5.2 is the AlertHistory table.


The following are the columns that are in the AlertHistory table:


SELECT TOP 1000 [AlertHistoryID]

































  FROM [SolarWindsOrion].[dbo].[AlertHistoryView]


This table is prebuilt in the 11.5.2 version.


If you could not view this table, the following commands are used to create it. This is a scripted view in 11.5.2.



USE [SolarWindsOrion]



/****** Object:  View [dbo].[AlertHistoryView]   ******/








Create view [dbo].[AlertHistoryView] as

      SELECT AH.[AlertHistoryID], ACo.AlertID, AH.[TimeStamp],

CASE AH.[EventType]

WHEN 0 then 'Triggered'

WHEN 1 then 'Reset'

WHEN 2 then 'Acknowledged'

WHEN 3 then 'Note'

WHEN 4 then 'AddedToIncident'

WHEN 5 then 'ActionFailed'

WHEN 6 then 'ActionSucceeded'

WHEN 7 then 'Unacknowledge'

WHEN 8 then 'Cleared'

Else 'Unknown'

END  as EventTypeWord ,

ACo.[Name], ACo.[ObjectType], ACo.[Enabled] as AlertEnabled, ACo.[Frequency],

AH.[Message], AH.[AccountID], AH.[AlertActiveID], AH.[AlertObjectID], AH.[ActionID], AC.ActionTypeID, AC.Title,

AO.RealEntityType, AO.TriggeredCount, AO.EntityNetObjectId, AO.EntityCaption, AO.EntityDetailsUrl, AO.RelatedNodeCaption, AO.RelatedNodeDetailsUrl, AO.RelatedNodeId, AO.LastTriggeredDateTime, AO.AlertNote,

ACo.[AlertRefID], ACo.[BlockUntil], ACo.[NotifyEnabled], ACo.[LastEdit], ACo.[CreatedBy], ACo.[Canned], ACo.[Category], ACo.[Severity]

  FROM [AlertHistory] AH With (Nolock)

  INNER JOIN AlertObjects AO With (Nolock) ON AH.AlertObjectID = AO.AlertObjectID

  INNER JOIN AlertConfigurations ACo With (Nolock) ON ACo.AlertID=AO.AlertID

  LEFT JOIN Actions AC With (Nolock) ON AH.ActionID = AC.ActionID




Last modified