How does EDA handle a connected SQL database going offline - do records get queued up & resent once the SQL database comes back online? (assumption is that we have a universe publisher/subscriber setup with replication & EDA is connected to a universe subscriber node)

Hi Mark,

Given the comment that Replication would be involved, you can review the behavior of Replication configuration parameter RW_IGNORE_ERROR.  Granularity was added to this parameter back around 11.3.1 I believe. One of the settings allows for suspending Replication if the EDA database is unavailable. When Replication is suspended, updates will queue until Replication is restarted. In this example, once the EDA database was back online, a sync command could be issued to continue replicating records.

Thanks,

Neil