OpenEdge Data Management: DataServer for Microsoft SQL Server

RDBMS stored procedure basics
When you run stored procedures concurrently, the DataServer uses one connection to
the data source per procedure. If different stored procedures attempt to update the
same record from a single client’s requests, the connections could block each other or
a deadlock might occur.
Notes: You must define a PROC-HANDLE phrase for each stored procedure phrase that
is simultaneously active. This technique provides a CLOSE STORED-PROC
statement that can identify the targeted open procedure and close it.
In contrast, since a stored procedure executed with the LOAD-RESULT-INTO
phrase implicitly closes the procedure once the execution ends and the data
retrieved is placed into temp tables, it essentially runs serially and has no use
for a PROC-HANDLE.
• When you create or update your schema image, the stored procedures appear in
the list of accessible objects along with tables, view, and sequences. OpenEdge
allows you to run the stored procedures that you create in data sources using the
procedure definitions in your schema image. See your Microsoft SQL Server
documentation for complete information about creating and using stored
procedures.
• If the ABL that executes a stored procedure is already within a transaction block,
the stored procedure becomes an extension of that transaction and will not
commit to the database until the ABL transaction is completed. However, because
the stored procedure does not execute as part of ABL client process, it cannot be
rolled back by ABL.
• The DataServer cannot roll back sub-transactions in the stored-procedure context
since it has no control over what the stored procedure executes.
The following section expands on the use of the RUN STORED-PROC statement.
OpenEdge Data Management: DataServer for Microsoft SQL Server 123