Stored proc activity with no params using Library variable connection to Azure SQL DB should't fail

We’ve identified a reproducible issue in Fabric Data Pipelines:

• ✅ Stored Procedure activity succeeds when using a library variable connection to Azure SQL Database and passing a parameter.

• ❌ The same activity fails with error 2812 (“Could not find stored procedure”) when no parameters are passed.

This suggests Fabric uses different execution paths depending on whether parameters are present — and the no-parameter path doesn’t resolve the stored procedure correctly.

Workaround:

Add a dummy parameter to the stored procedure, e.g.:

@forceContext NVARCHAR(255) = NULL

This forces Fabric to use the more reliable execution path.

Ask:

Please make Stored Procedure activity behave consistently regardless of whether parameters are passed — especially when using library variable connections. This would eliminate confusion and reduce brittle workarounds.