Forum Discussion
Copy activity from Oracle to Lakehouse fails without staging
Hi vietng Even if you're choosing a Lakehouse it may still be using the SQL Endpoint behind the scenes, since I'm guessing you're writing in the /Tables area. Trying opening the 1433 port and see if it works.
Hi vietng,
One small correction, if you're targeting a lakehouse, it wouldn't be using the SQL endpoint to write data as the sql endpoint is read only, but deborshi_nag is correct that it might still be using the SQL ports to do the data movement.
I always recommend opening all the ports found on this page when doing gateway maintenance:
Adjust communication settings for the on-premises data gateway | Microsoft Learn
Super UserHello vietng
A Staged Copy is necessary when port 1433 isn't open for SQL connections. Since ticking "Enable Staging" resolves the issue, it suggests that port 1433 is needed for your data copy. Usually, copying data to a Fabric Lakehouse or OneLake doesn't require outbound port 1433. Are you working with a SQL Warehouse or using a SQL Endpoint instead of a Lakehouse ? That might be why you're experiencing this issue.
You might want to whitelist this and see if that works.
Hi deborshi_nag
Thank you for your support. About your question, I use the Lakehouse connection in the Destination settings (select Browse all, then choose my Lakehouse in the list), so it can't be the SQL Warehouse or SQL Endpoint right?
