Which Fabric item copies on-premises SQL Server data to Warehouse1?
You have a Fabric workspace that contains a warehouse named Warehouse1. You have an on-premises Microsoft SQL Server database named Database1 that is accessed by using an on-premises data gateway. You need to copy data from Database1 to Warehouse1. Which item should you use?
Community Insight
This question tests which Fabric item can perform gateway-backed SQL Server-to-warehouse data movement, and the trap is assuming a notebook or Dataflow Gen1 is the natural copy tool.
Copying on-premises SQL Server data into a Fabric warehouse through an on-premises data gateway requires a Fabric item that supports gateway-backed data movement and a warehouse sink. This page establishes that a data pipeline with the Copy data activity is the correct choice, not Dataflow Gen1, a KQL queryset, or a notebook.
The most common wrong answer is a notebook because it can connect to SQL Server, but it is code-first and lacks the built-in gateway-backed Copy data activity; Dataflow Gen1 is also a trap because it is deprecated.
Community Discussion (18 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A data pipeline is the Fabric Data Factory item built for data movement and orchestration, and its Copy data activity can read from an on-premises SQL Server source through an on-premises data gateway and load the rows into Warehouse1. The gateway handles the network path to Database1, while the pipeline defines source, sink, mappings, and scheduling without custom code. Because this scenario asks only to copy data, not to transform it, the pipeline is the most direct and efficient fit. The data pipeline also aligns with the exam's expectation that Fabric Data Factory handles gateway-backed batch ingestion into a warehouse.Why the Other Options Are Wrong
A Dataflow Gen1 dataflow is not the right choice because Gen1 dataflows are deprecated in Fabric, and even Dataflow Gen2 is better suited when transformations are needed rather than a straight copy. A KQL queryset is a query surface for KQL databases and Eventhouse data; it cannot serve as the ingestion mechanism from SQL Server into a warehouse. A notebook is code-first and can connect to many sources, but it does not provide the built-in gateway-backed Copy data activity and would require custom movement code. The exam expects the native Fabric data-movement item when the source is on-premises and the destination is a warehouse.Community Comment Notes
The discussion overwhelmingly favors a data pipeline: robertlavigne noted that notebooks cannot go through a gateway, KQL is not appropriate for a SQL database, and "Gen1 dataflows are deprecated", while sesav4742 and mmanrik emphasized the Copy data activity as the efficient path for a no-transformation copy. Thatoyaka summarized that pipelines support on-premises SQL Server via the gateway and Warehouse as a sink. Tuki93 reinforced the elimination of Dataflow Gen1 by stating "Dataflow Gen 1 is deprecated." A minority comment from arunmewada chose A, but it supplied no reasoning and is outweighed by the deprecation and gateway-support arguments.Official Reference
Exam Strategy
When the question mentions an on-premises source plus an on-premises data gateway, look for the Fabric item that natively supports gateway connections and a Copy data activity. Eliminate Dataflow Gen1 on deprecation grounds and KQL querysets because they query KQL databases, not SQL Server.
Frequently Asked Questions
Why not use a Dataflow Gen1 dataflow to copy Database1 into Warehouse1?
Dataflow Gen1 is deprecated in Fabric, so exam answers favor a data pipeline with Copy data for a direct gateway-backed load from SQL Server to a warehouse.
Why is a KQL queryset not correct for Database1?
A KQL queryset queries KQL databases in Eventhouse; it is not a general data-movement item and cannot copy SQL Server tables into Warehouse1.