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

[vasalari]

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

[SQL_Data_101]

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

[V-yubandi-msft]

Hi @vasalari ,

Could you let us know if your issue has been resolved or if you need any additional information? If the issue is resolved, please mark it as the Accepted Solution. This helps other members who might be facing similar issues.

[V-yubandi-msft]

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.

[V-yubandi-msft]

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.

[V-yubandi-msft]

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.

[nilendraFabric]

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-C...

if this is helpful please accept the answer and give kudos