How to shift from Replace to Append Mode for RedShift tables without loosing data ?
Hi,
We have connected a bunch of massive volume of data to Domo by connecting to our RedShift database. Some of those tables are 50M+ rows and the nightly sync of those becomes longer and longer as we position them as "replace".
Can you share best tricks to move Domo to an "append" mode while ensuring that there's no data gap or data duplication by doing so?
Currently we had to stop a few of the bigger tables to be ingested (300M+ rows / 12Gb + datasets) and some of our tables takes more than 8 hours to sync.
Thanks in advance
Comments
-
@pierreeric I understand @zcameron has been working with you on this. Once its sorted out you can share back the solution.
Thanks!
1 -
The only acceptable and efficient way we found to safely move RedShift tables to "Append" mode in domo was to do the following:
1 - pre-generate a RedShift view on the RedShift side that only captures the updated data from the day before (cleared of duplicates or missing entries)
2 - then and only then connect this "day minus one" view as the datasource in Domo and toggle it into append mode mechanism.
Step 1 being very important as you can control on RedShift what the data should be (free of duplicates or data gaps) - something Domo cannot ensure.0
Categories
- All Categories
- 1.1K Product Ideas
- 1.1K Ideas Exchange
- 1.2K Connect
- 969 Connectors
- 257 Workbench
- Cloud Amplifier
- 1 Federated
- 2.4K Transform
- 76 SQL DataFlows
- 501 Datasets
- 1.8K Magic ETL
- 2.7K Visualize
- 2.2K Charting
- 375 Beast Mode
- 20 Variables
- 485 Automate
- 103 Apps
- 378 APIs & Domo Developer
- 6 Workflows
- 22 Predict
- 6 Jupyter Workspaces
- 16 R & Python Tiles
- 316 Distribute
- 64 Domo Everywhere
- 252 Scheduled Reports
- 59 Manage
- 59 Governance & Security
- 1 Product Release Questions
- 5K Community Forums
- 37 Getting Started
- 23 Community Member Introductions
- 63 Community Announcements
- 4.8K Archive