Automatic Failover so You Are Always Open for Business
The ETL process to an SQL server works fine, but what happens when something goes wrong?
When you define an SQL ETL process for RavenDB, RavenDB assigns it to one of the nodes in the database cluster. If that particular node goes offline, RavenDB will assign the task to another available node. Everything will continue as usual as these changes are transparent to RavenDB clients.
If the destination database goes offline, no worries. RavenDB will simply remember the last successful change that was sent via the ETL process, and once the destination database comes back online everything will get back to normal.
This maximizes availability for your database systems, making your database as resilient to unpredictability inherent in distributed systems as it can be.