Error when called StoreProcedure from Pipeline / failed to generate query plan

[GHerz]

Dear all, 

I am calling a stored procedure in my Fabric DWH from a pipeline. 

The Proc is for incremental data load. 

It performs the following operations in order to merge a table with new/modified records into the main table.

- Update modified records

- Insert new records

That works well for a lot of tables, but for few tables I'm get the following error message during the update step:

"Request to perform an external distributed computation has failed with error "100001;Failed to generate query plan.".

Statement ID: {C98...."

Can someone help with an idea what this is about and how to solve?

Thanks and best regards!!

[KSB1234]

I have a similar problem , My StoreProcedure is  doing Update and insert opwration, but when i am running in the Pipeline with the StoredProcedure Activity and also script activity the updae and insert statement not populating correctly. Please give a suggistion how to solve it.

Thanks,

kavya Bhat.

[Anonymous · Accepted solution]

Hi @GHerz ,

I noticed in your error you mentioned “100001;Failed to generate query plan.”. This error is due to a query plan generation issue in distributed environments such as Microsoft Fabric DWH.

Sometimes, complex queries, especially those involving COUNT(DISTINCT ...) can cause problems. Simplifying the query or using a function such as APPROX_COUNT_DISTINCT may help.

Errors may be related to the distribution of queries across nodes. Ensure that data distribution and degree of parallelism (DOP) are properly configured.

If you want to know more about this error, I think you can look at this topic: PolyBase error - 100001;Failed to generate query plan. - Microsoft Community Hub

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[GHerz]

Dear Yilong Zhou

your comment pointed me in the right direction. 

My Procedure, that runs in the DWH, uses a view from the Lakehouse. 

I tried to materialize the view into a DWH Table and using this table instead seems to solve my problem.

Thanks, Gunnar