Forum Discussion
Data Ingestion to Fabric SQL Database
I am trying to insert a relatively small amount of reference data into a newly created Fabric SQL database, but every method I try fails with an error. For instance, if I follow the instructions at Insert data using a Microsoft Fabric Pipeline on learn.microsoft.com, I can connect to the odata feed but then PowerQuery throws an error:
An error occurred while evaluating the destination query: DataSource.Error: Downstream service call to url 'https://wabi-uk-south-c-primary-redirect.analysis.windows.net/v1/workspaces/.../items?type=SQLDatabase' failed with status code 404.
Alternatively, if try a copyjob I get the following error:
Fabric activity failed. ' Error occured while trying to get FabricSqlConnectionInfo. Please retry later. Detailed Message: 'StatusCode: NotFound, WorkspaceId: xxx, ArtifactId: xxx, Error Code: ItemNotFound, Message: Could not found the requested item, Request ID: xxx, Content: {"requestId":"xxx","errorCode":"ItemNotFound","message":"Could not found the requested item","isRetriable":false}' '.
I can open the Fabric SQL database fine in SSMS and have created tables, etc.
What I can't get my head around is that I have access to another tenant where this all works correctly and is very easy to set up. The tenant where this works is using a Fabric Trial, the non-working Fabric is an F64.
What could be wrong in the F64 ?
6 Replies
Make sure you are interacting with the actual database, not with its SQL Analytics Endpoint. That one is read-only.
Hi Stat,
Thank you for posting your query in the Microsoft Fabric Community Forum.
Based on the official Microsoft Fabric documentation, loading data into a SQL database using Data Factory pipelines or copy activities requires that the SQL database is properly accessible within the same Fabric workspace and capacity context where the pipeline is executed.
The NotFound / ItemNotFound / FabricSqlConnectionInfo errors you are encountering typically indicate that the SQL database item is not being successfully resolved by Fabric services during pipeline execution. While you are able to connect through SSMS, this only validates T-SQL connectivity to the SQL endpoint. Data Factory pipelines additionally depend on Fabric service-level metadata and item resolution within the workspace.
According to Microsoft documentation:
- The workspace must be assigned to a Fabric capacity for Data Factory operations involving Fabric items.
• Data pipelines interact with Fabric items (such as SQL databases) through workspace-scoped artifacts, and correct workspace association is required.
• SQL database in Fabric has certain limitations and evolving capabilities, which can impact ingestion scenarios depending on configuration and readiness.
In scenarios where the same workflow works in a Fabric Trial but not in another capacity, this is typically related to differences in workspace configuration, item state, or feature enablement rather than the capacity SKU itself.
you may consider:
- Verifying that the SQL database, pipeline, and workspace are all within the same Fabric-enabled capacity
- Revalidating the SQL database selection in the pipeline (to ensure correct item reference)
- Confirming that the workspace region and configuration support SQL database ingestion scenarios
You can refer to the following official documentation for more details:
Limitations for SQL database - Microsoft Fabric | Microsoft Learn
Load data with pipelines into SQL database - Microsoft Fabric | Microsoft Learn
Thanks, lbendlin for sharing valuable insights.
Best regards,
Ganesh Singamshetty- The workspace must be assigned to a Fabric capacity for Data Factory operations involving Fabric items.
Hello Stat,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
Not resolved as yet. I have tried a few other investigations (spun up another Fabric capacity for comparison, etc) but still no luck.
I've logged a support request now & will share here when we get this resolved.Hello Stat,
Thank you for sharing the update. Please post the resolution in the community, as it will benefit other members who may be experiencing similar issues.
Hi Stat, hope you are doing well. Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues. If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.
