Integration with relational databases

Integration with relational databases

RavenDB SQL ETL Lets You Work with Relational and Non-Relational Databases Alike

RavenDB gives you the ability to send and transform data from one place to another. Enjoy built-in support for ETL processes to relational databases like Microsoft SQL, Oracle, PostgreSQL, MySQL, and more.

This empowers you in several areas:

  • Microservices. RavenDB replicates data in real-time enabling you to move information from one service to another and reap the benefits of a microservices architecture. Use RavenDB ETL to distribute a set of records to related services without making a cross-service call. Change the shape of your data to fit the demands of other services.
  • Privacy. Keep your data private when sending it across the wire. Obscure information by stripping it of private details to protect clients, users, and third parties. Great for health care applications. Ideal for applications that share information about users while protecting their private data.
  • Integrate with Existing BI Systems. Use your RavenDB SQL ETL to connect with relational OLAP databases. Process your data quickly and seamlessly with your document database and pass it on to your OLAP system for real-time reporting and analysis.

It’s fantastic for point of sale systems where you can take in data right at the edge point and immediately send it from hundreds of cash registers to a central server. In a moment’s notice, you can assess the financial status of your organization.

Fit Document Data Into RDBMS

Translating between the document model and the relational model is no simple matter. RavenDB enables you to “change your data modeling” (normalize your data to fit into a DBMS model) in flight to share between RavenDB and SQL data store.

RavenDB will also make updates to your relational database whenever a document is changed. It’s done in an async and resilient manner. Just provide a connection string and specify how you want your data to be transformed during the ETL process.

Moving your data from a Document Model to an RDBMS can be done by simply writing the transformation you want using JavaScript, and let us handle the rest.

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.