This article answers frequently asked questions about Mirroring Snowflake in Microsoft Fabric.
For Snowflake, we do use a landing zone to store both the snapshot and change data into OneLake, to improve performance as we're converting these files in the landing zones into delta vertiparquet.
Currently, only replicating regular tables are supported.
Select the settings cog, then select on Manage connection and gateways. You can also delete existing connections from this page.
Implement Snowflake budgets, use limits on credits, or use dedicated a smaller Snowflake instance based on requirements.
Fabric doesn't charge for Ingress fees into OneLake for Mirroring.
If hosted outside of Azure, refer to Snowflake and your cloud documentation for egress costs. If hosted in Azure but in a different region from your Fabric capacity, data egress will be charged. If hosted in Azure in the same region, there is no data egress.
It depends on the size of the data that is being brought in.
Near real-time latency.
Yes, tables are all v-ordered delta tables.
Currently, access through the Power BI Gateway or behind a firewall is unsupported.
The data from source tables will be reinitialized. Each time you stop and start, the entire table is fetched again.
We stop Mirroring that specific table and delete it from OneLake.
No, we just remove the streaming tables.
Yes, you can, but you shouldn't need to. Once the data is in Fabric, it can be shared from there.
Yes, specific tables can be selected during Mirroring configuration.
No.
No, data isn't staged outside of customer environment, it's staged in the customer's OneLake.
A Power BI Premium, Fabric Capacity, or Trial Capacity is required. For more information on licensing, see Microsoft Fabric licenses.
There's no cost for Mirroring or storing mirrored data in Fabric, unless storage exceeds provisioned capacity.