Database replication, effortlessly
Few steps - many methods!
Choose your replication method
Support your specific use-case
Change it in the stream
All your data is secure
Database replication FAQ
Think of data replication like making periodic, cumulative, automatic backups of your database. These backups can be one-off, incremental, or even continuous. Simply put, data replication takes data from your source database — Oracle, MySQL, Microsoft SQL Server, PostgreSQL or MongoDB — and copies it to the cloud. Because your data warehouse is the most important means to access and analyze your data, data replication is essential. Otherwise you could end up with missing or duplicated data. Learn more about database replication.
Full Dump and Load: you define a replication interval; at each interval, your specified tables are queried and a complete snapshot is taken. The new snapshot replaces the previous snapshot in your DW.
Best for small tables, updated every few hours.
Incremental Replication: you define an
update_indicatorcolumn for each table you want to replicate. The value in that column is used to determine whether the row needs to be loaded.
Tables on the source are queried for changes based on the indicator column. These incremental changes are then copied to your target DW. You can see the changes in near real time.
Best for larger tables, updated periodically.
Change Data Capture (CDC) or Log Replication: this is the state of the art in database replication, being the fastest and most reliable method. In this method, you set up a source database's internal change log to be queried to get the latest changes. This log is copied to the target DW and merged frequently.
Enables near-real-time replication with low query impact on the database. Databases must support this functionality (Microsoft SQL Server, MongoDB, MySQL, Oracle, and PostgreSQL).
Database mirroring is where an entire database — tables, schemas, and data — is copied in its entirety, with no changes, to another location. It's essentially a duplication. Mirroring involves two copies of the same database residing at different locations.
Database replication, supported by Alooma, involves copying only data and database objects to another existing database. Database replication may allow for changes to the data or database objects in transit, so that optimizations can be made between source and destination.
Mirroring can be used in conjunction with replication to improve database availability.
Whether you need to prioritize simplicity, speed, thoroughness, or all of the above, selecting the right data replication method has a lot to do with your particular source database and how you store and collect data.
Alooma supports three different methods of database replication: full dump & load, incremental, and change data capture (CDC) — each with a minimal footprint in your data warehouse. Alooma manages the complexities of database replication so you don't have to, and puts the solution at your fingertips.