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
There are limitations when executing multiple store procedures, including nested procedures, in a SQL Server environment as a transaction.
The execution terminates before the nested procedures complete. This is likely due to SQL - if at any point the procedure fails, the entire transaction will roll back. This disrupts the intended flow.
Managing metadata for stored procedures during development cycles has become difficult to manage.
Describe the solution you'd like
Seeking a solution to allow seamless execution of multiple store procedures, possibly nested, as a transaction. All procedures must execute fully and correctly.
Enhanced flexibility and improved usability, particularly in managing stored procedure metadata, would be highly beneficial.
Describe alternatives you've considered
Connecting and tracking stored procedures - insufficient due to limitations with nested procedure handling.
Native Query - restriction against using the "exec" keyword rendered this approach ineffective. Also does not support nested transactions.
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
There are limitations when executing multiple store procedures, including nested procedures, in a SQL Server environment as a transaction.
The execution terminates before the nested procedures complete. This is likely due to SQL - if at any point the procedure fails, the entire transaction will roll back. This disrupts the intended flow.
Managing metadata for stored procedures during development cycles has become difficult to manage.
Describe the solution you'd like
Seeking a solution to allow seamless execution of multiple store procedures, possibly nested, as a transaction. All procedures must execute fully and correctly.
Enhanced flexibility and improved usability, particularly in managing stored procedure metadata, would be highly beneficial.
Describe alternatives you've considered
Connecting and tracking stored procedures - insufficient due to limitations with nested procedure handling.
Native Query - restriction against using the "exec" keyword rendered this approach ineffective. Also does not support nested transactions.
The text was updated successfully, but these errors were encountered: