Forum Discussion
Post ProdigyUsing the Mirroring feature in a data warehouse project
Yes, Mirroring is a great accelerator for bronze if you want that layer to be raw, untransformed data from your source environment. I've used mirroring in a medallion architecture with good success. At that point it's Delta tables sitting in your OneLake, which can be consumed for processes to move your data into silver.
Post ProdigyHi,
when I talk about a lakehouse I refer to the object and not to the related shortcut.
I'd like to understand if Mirroring feature could be really useful in a medallion architecture to implement a data warehouse: it seems to be a valid alternative respect to a lakehouse in the bronze layer; so, Mirroring feature could be an accelerator component to deliver a data warehouse solution, isn't it?
Next, at silver layer I could have a lakehouse that reads from the bronze mirrored data source and so on.
I've already read the documentation about this feature.
Thanks
Most Valuable ProfessionalYes, Mirroring is a great accelerator for bronze if you want that layer to be raw, untransformed data from your source environment. I've used mirroring in a medallion architecture with good success. At that point it's Delta tables sitting in your OneLake, which can be consumed for processes to move your data into silver.
- pmscorca
Hi, thanks for your reply.
It seems that Mirroring supports only some data sources. Could I use Mirroring for an Oracle or MySQL source? Open mirroring?
Thanks
- DataBard
In current state, you'd have to use Open Mirroring for Oracle or MySQL.
dbWizardAdvocate I
My issue is when mirroring breaks and requires full rebuild. Then all the downstream dependencies fail. I'm thinking I mirror data to fabric, then have a process to immediately copy that data into a lakehouse to provide a buffer and layer of redunancy while items can be pointed at the lakehouse instead of mirror database so in the even that mirroring breaks we can keep on trucking while mirroring gets fixed. Thoughts?