topic on-premise data warehouse to fabric data warehouse using gateway directly in Data Warehouse

on-premise data warehouse to fabric data warehouse using gateway directly

vasalari — Tue, 18 Feb 2025 18:44:23 GMT

Is it possible to copy tables from on-premise SQL data warehouse to Fabric data warehouse directly using Getway.

I understand we can do it by copying to Lakehouse and then to Warehouse. I have huge tables and this happens daily. I need direct to data warehouse

Re: on-premise data warehouse to fabric data warehouse using gateway directly

nilendraFabric — Tue, 18 Feb 2025 21:30:48 GMT

Hello vasalari

Copying data directly from an on-premises SQL data warehouse to a Fabric data warehouse using the gateway is not currently supported, requiring an intermediate step through a lakehouse.

Dataflows Gen2 can bypass staging requirements and load directly into Warehouse if configured correctly, though this method has limitations for large datasets

https://datamozart.substack.com/p/how-to-bring-sql-server-data-into

The limitation stems from Fabric Warehouse’s reliance on external staging for pipeline ingestion, unlike Lakehouse’s native OneLake integration. Microsoft has acknowledged this inconsistency ,but direct gateway-to-warehouse transfers remain on the roadmap without a confirmed ETA

https://community.fabric.microsoft.com/t5/Data-Pipeline/On-Prem-SQL-Server-to-Fabric-Warehouse-via-Copy-Data/m-p/3807921

if this is helpful please accept the answer and give kudos

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Wed, 19 Feb 2025 09:44:37 GMT

Hi vasalari ,

Thanks for contacting the Microsoft Fabric Community. As nilendraFabric mentioned, direct gateway to warehouse ingestion is not supported yet because Fabric Warehouse requires external staging, unlike Lakehouse's native OneLake integration.

Additionally, the Dataflows Gen2 approach can load data directly into the warehouse if configured correctly, but it may face challenges with very large datasets.

Given your large tables and daily loads, We recommend the following.

Incremental Refreshes - Load only the changed data daily instead of the entire dataset.
Partitioning Strategies - Divide the data into manageable chunks to speed up ingestion.
Automate with Fabric Pipelines - Reduce manual work and ensure consistency.

If you have ideas to share, please visit the following link

https://ideas.fabric.microsoft.com/ideas/search-ideas/

If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Tue, 25 Feb 2025 11:37:10 GMT

Hi vasalari ,

Could you please confirm whether your issue has been resolved or if you are still experiencing any problems? Your feedback is valuable to the community as it helps others who might be facing a similar issue.

If the issue is resolved, please mark it as the Accepted Solution to assist others in the community in finding the answer more easily.

Regards,

Yugandhar.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Sat, 01 Mar 2025 17:11:23 GMT

Hello vasalari ,

Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems.

Thank You.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Tue, 17 Jun 2025 15:22:51 GMT

Hi vasalari ,

Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.

If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.

Thank you for being part of the Microsoft Fabric Community.

— Yugandhar
Community Support Team.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

SQL_Data_101 — Mon, 17 Mar 2025 20:15:12 GMT

In SQL, there are several tasks we typically perform, such as analyzing execution plans, creating or updating indexes, identifying and terminating blocking queries, and monitoring resource usage. However, I'm wondering how these tasks are handled within Microsoft Fabric.

Specifically:

How do you check the execution plan and optimize queries without using indexes?
How can you identify which queries are blocking others or consuming excessive resources?
How do you manage session resources, such as killing sessions that use too much?
Is there a way to monitor schema or table capacity usage in Fabric?
Is there an alternative to materialized views for pre-computing and storing query results for performance optimization in Fabric?
How can I replicate the functionality of synonyms in Fabric, or how should I handle object references across different databases or schemas?
What are the recommended alternatives to temporary tables for session-based or short-lived data storage in Fabric?
How can I monitor schema or table-level capacity usage in Fabric to track resource consumption?
Actually looking for Daiyly activities of DBA

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Tue, 17 Jun 2025 15:20:16 GMT

Hi SQL_Data_101 ,

In Microsoft Fabric, cross database queries and the use of synonyms common in traditional SQL Server environments are not currently supported. Instead, the recommended approach is to use Lakehouse shortcuts, which allow you to reference tables from other Lakehouses or even across workspaces without physically duplicating the data. This method is effective in Lakehouse scenarios.

However, within a Data Warehouse, the current limitation requires that all tables involved in joins be located in the same workspace and warehouse. Therefore, it may be necessary to replicate or move the required tables to ensure compatibility and seamless querying.

This approach offers flexibility in Lakehouse environments, but for Warehouse based use cases, it is essential to plan your data structure within workspace boundaries to support your query requirements.

Here is a community idea request pointing out the lack of synonyms in Fabric Warehouse and noting that it's still an open request synonyms are not currently supported.

Support Synonyms in Fabric Warehouse - Microsoft Fabric Community

Helpful References:

Unify data sources with OneLake shortcuts - Microsoft Fabric | Microsoft Learn

SQL database Overview (Preview) - Microsoft Fabric | Microsoft Learn

Regards,

Yugandhar.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

vasalari — Tue, 17 Jun 2025 16:10:06 GMT

I Have DataWarehouse_1 (DW) in WorkSpace_1 (WS) and DW_2 in WS_2. Using shortcut thru Lakehouse I join tables from two DWs. It is working for me

Re: on-premise data warehouse to fabric data warehouse using gateway directly

V-yubandi-msft — Wed, 18 Jun 2025 08:45:21 GMT

Hi vasalari ,

Glad to hear it's working fine. I’ll mark this as the accepted solution so it can help other community members who might face a similar issue.

Thank You.

Re: on-premise data warehouse to fabric data warehouse using gateway directly

jasonhill01 — Thu, 10 Jul 2025 06:17:27 GMT

Yes, currently there's no direct way to copy from on-prem SQL to Fabric Data Warehouse using Gateway. The supported path is via Lakehouse first, then to Warehouse. I agree for large daily loads, a direct route would be ideal. Hopefully, Microsoft adds this soon!