Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
The Dataflow indicates a successful connection to the SQL Database (preview) or Lakehouse; however, no data is being transferred. Despite the connection status showing as active, the data does not appear to be flowing from the Dataflow to the target destination.
Could someone advise on potential solutions or troubleshooting steps for this issue? Thanks.
Solved! Go to Solution.
Open Dataflow Editor โ Check the preview of your final query.
Ensure rows are returned.
Enable Load to Destination:
Right-click the final query โ Click โEnable loadโ (if not already enabled).
Check Schema Compatibility:
Make sure column names and data types match the destination (SQL DB or Lakehouse).
Test with a New Table:
In output settings, write to a new table name to avoid conflicts.
Re-authenticate Connection:
Go to Manage connections โ Click Edit icon โ Re-authenticate SQL or Lakehouse connection.
Review Refresh History:
Go to Dataflow settings โ View refresh history โ Look for errors or โ0 rows written.โ
If no data is showing in the preview, the issue is with the source query or connection, not the destination.
Open Dataflow Editor โ Check the preview of your final query.
Ensure rows are returned.
Enable Load to Destination:
Right-click the final query โ Click โEnable loadโ (if not already enabled).
Check Schema Compatibility:
Make sure column names and data types match the destination (SQL DB or Lakehouse).
Test with a New Table:
In output settings, write to a new table name to avoid conflicts.
Re-authenticate Connection:
Go to Manage connections โ Click Edit icon โ Re-authenticate SQL or Lakehouse connection.
Review Refresh History:
Go to Dataflow settings โ View refresh history โ Look for errors or โ0 rows written.โ
If no data is showing in the preview, the issue is with the source query or connection, not the destination.
Hi @js15 ,
May I ask if the provided solution helped in resolving the issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you!!
Just did, thank you.