A client this week had a MSSQL database reach its size limit and stop logging. This was corrected, and initially we thought that we hadn’t lost any data because the tag history was set up through a tag splitter to also log to a remote SQL database. As it turns out, the remote database had suffered a failure two days before due to a completely unrelated networking problem.
The client has noted that their historical data redundancy measures were ineffective because they were not alerted to the failure of one of the databases until the other also failed, and wish to correct this.
How can I generate an alarm/set a tag value based on the connection status of a database connection?
As an aside - it was only the master server that had the connectivity issue - the backup server could connect fine, but because the master server was communicating fine with the backup server, the backup server was in standby and didn’t log any data to the remote database either.
Using Ignition 7.9.9