I know that RavenDB has a replication bundle, but that only seems to support replication from RavenDB into SQL server. I would like to do that the other way around. The only way I known to keep Raven up to date with data in a SQL database would be to run a series of triggers from sql and update raven accordingly. This just sounds like a maintenance nightmare waiting to happen. Is there a better way to keep a RavenDB database in synch with a sql database, where the raven database is acting as a slave, not a master?
I would suggest using a CLR trigger for this. You can set the trigger to fire at the database level and then capture the eventdata and fire up the raven session and log it into the raven database.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With