You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m not sure if this idea makes sense (it does in my head, but I’m open to discussion).
As far as I know, with DAB we can expose stored procedures that may take time to finish. Since it’s a synchronous API, that means I need to keep the connection open until the stored procedure completes.
Wouldn’t it be useful to have the option to flag the API as “async”?
That way, I could support parallelization scenarios (even directly in SQL Server 2025 using sp_invoke_external_rest_endpoint), while letting the database do the work and only polling occasionally for the processing status.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I’m not sure if this idea makes sense (it does in my head, but I’m open to discussion).
As far as I know, with DAB we can expose stored procedures that may take time to finish. Since it’s a synchronous API, that means I need to keep the connection open until the stored procedure completes.
Wouldn’t it be useful to have the option to flag the API as “async”?
That way, I could support parallelization scenarios (even directly in SQL Server 2025 using sp_invoke_external_rest_endpoint), while letting the database do the work and only polling occasionally for the processing status.
Beta Was this translation helpful? Give feedback.
All reactions