Advocate IIIBUG: Fabric pipelines stored procedure activity does not update target correctly after deployment
I have a data pipeline that uses the stored procedure activity to call a sproc in a warehouse in the same workspace. This works fine in dev, but after using the deployment pipeline and running in the test workspace, I get the below error:
The server address cited in the error message is indeed for the dev workspace, but when I look into the source code for the activity, I see that the connection details are correctly listed as the test workspace server address and workspace ID:
I've also checked the JSON definition of the entire pipeline and can't find any reference to the dev workspace server name either, so I'm not sure why it's attempting to access the dev workspace. The only fix for this appears to delete and recreate the activity in the test environment, invalidating the pipeline. As such, I believe this is a bug in the pipeline activity feature and requires fixing.
Procedure runs successfully when directly executed in SSMS
2 Comments
- We also have experienced this issue on our deployments for the last several weeks.
Yup, finding exactly this problem. I have a working pipeline with a Warehouse sp-based Lookup activity in Dev. I deploy to prod and all the *JSON* I can see suggests everything's worked fine and the warehouse endpoint has been updated to the prod value. But actually running the activity fails because it tries to connect to the dev endpoint. Simply "save as" fixes it -- the new copy of the pipeline works fine.
This is really annoying as it means I can't use deployment pipelines without manually going into each pipeline after deployment, making a tiny change and re-saving them in prod, after which they work, but that kinda obviates the entire point of a deployment pipeline, of course...
