1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Depends a lot on your situation, the three options are valid.
If you can join and aggregate in Oracle is the most efficient if you just need that, as long as the DB has spare capacity for it.
If you have some Zero-ETL to move the tables into Redshift, that avoids adding a tool and then you can do it there.
And if you already have an ETL like Glue or need it for something else, then you could do it there and avoid pushing the workload the Redshift
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
Thanks Gonzalo. As we already use Glue for other ETLs, I think the third option is the most feasible. Agree, first is the best, but there are limitations as to how much leverage we have on running expensive queries on the third party owned oracle db server.