topic Re: Mirroing vs shortcuts costing in Data Engineering

Mirroing vs shortcuts costing

Anonymous — Wed, 09 Oct 2024 19:47:25 GMT

Hi,

I'm looking to see which one has more cost involved, we have several tables in Azure Databricks

for some reasons we are looking to create a Data Lakehouse in Fabric to consume this data however the concern I have is which one is more costing either create a Shortcut from the Azure Databricks Lakehouse or if Mirroring

thanks

Re: Mirroing vs shortcuts costing

Anonymous — Thu, 10 Oct 2024 05:59:08 GMT

Hi @Anonymous,

Shortcut feature provides a direct link to the data without moving it.(it will create a reference to the data stored in another location)
This can be useful for real-time data access and reducing storage costs because it doesn't involve data replication.

Mirroring feature will create full copy of the data within Fabric, enabling advanced analytics and integration with other Fabric services. (this can simplify data management and improve performance for analytics workloads)
It will spend higher due to the replication of data into Microsoft Fabric's OneLake. (includes compute costs on the source system for data changes and cloud services compute costs)

In summary, shortcuts are cost-effective for real-time access without data movement, while mirroring offers more robust integration and analytics capabilities at a higher cost.

Regards,

Xiaoxin Sheng

Re: Mirroing vs shortcuts costing

Anonymous — Tue, 15 Oct 2024 07:07:42 GMT

Hi @Anonymous ,

Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.

If these also don't help, please share more detailed information and description to help us clarify your scenario to test.

How to Get Your Question Answered Quickly

Regards,

Xiaoxin Sheng