Stored proc activity slow from fabric pipeline

[Amit_K]

Hi fellow fabricators,

Has anyone experienced slowness with stored proc activity from Fabric data pipelines.

The procs when executed directly (via SSMS ) take less then 4-5 secs but from Stored proc activity, all upwards of 20 secs. The execution duration (in the activity output) shows 7-8 secs though.

Is this a pipeline issue with most of the time spent initialising connections with fabric warehouse? Can anything be done about it?

Cheers,

Amit

[Anonymous]

HI @Amit_K,

Any update on this? Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.

If these also don't help, please share more detailed information and description to help us clarify your scenario to test.

How to Get Your Question Answered Quickly 

Regards,

Xiaoxin Sheng

[Amit_K]

Hi,

I think, this issue needs to be looked into by the support team. 10-12 seconds to initialise a connection to a fabric warehouse seems excessive. Especially, when there will be 10s of stored procs to be executed as part of a daily pipeline which needs to run many times in a day.

Thanks,

AK

[Anonymous · Accepted solution]

HI @Amit_K,

I think they processed as your descriptions.
When you directly execute it on the SSMS, they required backend environment and data source connection is ready, so that you can use this quickly.
When you invoke it in pipeline, it needs to initializing required library and resources of pipeline and data warehouse, then create vailed connection as the prerequisite for the execute SP. (the additional spend that you mention)

Regards,

Xiaoxin Sheng