I have some event notifications that are triggered when some attributes are "on". There are a few of them that have been in the "on" state since the event were created. This weekend, there were updates installed to our SQL servers and they were rebooted. Our AF connects to a SQL database that is in a high availability always on cluster. When the primary server was rebooted, the events were triggered.
I was wondering if someone could explain how the status of the events are stored, why this might have happened, and how to avoid it.