Share via

Stored procedure transformation always on queued

Mustafa Ispir 46 Reputation points
2024-04-30T09:25:25.9133333+00:00

Hello ,

I have 2 environment dev and test.

There is a stored procedure which run successfully on dev bot queued on test for hours.

What are the possible causes for that ?

User's image

It runned successfully on dev in 1m on datafactory and 5 second on database.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,715 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. PRADEEPCHEEKATLA-MSFT 79,141 Reputation points Microsoft Employee
    2024-04-30T13:42:20.4433333+00:00

    @Mustafa Ispir - Thanks for the question and using MS Q&A platform.

    There could be several reasons why the stored procedure transformation is queued on the test environment. One possible reason could be hitting concurrency limits, service outages, network failures, and so on.

    To troubleshoot this issue, you can follow the below steps:

    • If your pipeline has a concurrency policy, verify that there are no old pipeline runs in progress.
    • Go to the ADF authoring canvas, select your pipeline, and determine if it has a concurrency property assigned to it. If it does, go to the Monitoring view, and make sure there's nothing in the past 45 days that's in progress. If there is something in progress, you can cancel it, and the new pipeline run should start.
    • It is possible that your run was impacted by a transient network issue, credential failures, services outages, etc. If this happens, Azure Data Factory has an internal recovery process that monitors all the runs and starts them when it notices something went wrong. You can rerun pipelines and activities as described here: Rerun pipelines and activities. This process happens every one hour, so if your run is stuck for more than an hour, create a support case.

    For more details, refer to Azure Data Factory: Pipeline status is queued or stuck for a long time.

    If none of the above steps help, you can check the Azure Data Factory logs to see if there are any errors or warnings related to the stored procedure transformation. If you are still unable to resolve the issue, please provide more information about your pipeline and the activities involved and ADF region so that we can investigate further.

    Hope this helps. Do let us know if you any further queries.

    0 comments