Forum Discussion
Copy Job from on prem SQL to Fabric SQL Database Error
Hi User,
The error suggests that the Copy Job can resolve the destination during configuration, but fails to retrieve the required connection information at runtime. Since you can browse and query the Fabric SQL Database successfully, this is likely a runtime resolution issue rather than a connectivity issue.
A few things to check:
Verify that the Fabric SQL Database still exists in the same workspace and hasn't been renamed, recreated, or moved after the Copy Job was created. Recreating the Copy Job can sometimes resolve stale artifact references.
Confirm that you have the required permissions on both the workspace and the Fabric SQL Database.
If you're using an On-premises Data Gateway, ensure it's online and updated to the latest version.
Try creating a new Copy Job with the same source and destination to rule out an issue with the stored ArtifactId.
Check whether the problem is reproducible with another Fabric SQL Database in the same workspace. If it is isolated to one database, the artifact metadata may be inconsistent.
Since the error returns ItemNotFound while the item is visible in the workspace, it may indicate a service-side metadata or runtime issue. If the problem persists after recreating the job, consider opening a Microsoft Support ticket with the Workspace ID, Artifact ID, Activity ID, and run timestamp.
For more information:
Copy Job in Microsoft Fabric: https://learn.microsoft.com/fabric/data-factory/copy-job
SQL Database in Microsoft Fabric: https://learn.microsoft.com/fabric/database/sql/overview
On-premises Data Gateway: https://learn.microsoft.com/data-integration/gateway/service-gateway-onprem
Could you also clarify:
Is the destination a Fabric SQL Database or a Warehouse?
Was the SQL Database created before the Copy Job, or was it recreated afterward?
Does the issue occur with all Copy Jobs targeting Fabric SQL Database, or only this specific one?
These details will help determine whether this is a configuration issue or a known service-side limitation.
💡 Helpful? Give a Kudos 👍 — keep the community growing.✅ Solved your issue? Mark this as the Accepted Solution ✔️Best regards, |