Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

CREATE PROCEDURE _SEQP_nextcustnum... is being displayed on the MS SQL Server sysprocess table when creating sequence using ABL NEXT-VALUE() using MS SQL Server DataServer

The following ABL query is run to create customer on the Sports2000 on MS SQL Server:

/***********************************/
CREATE customer.
ASSIGN
custnum = NEXT-VALUE(nextcustnum)
name = "test"
.
/***********************************/

The CREATE PROCEDURE ... is only visible when manually querying the MS SQL Server using the following query:

SELECT SPID, blocked, hostprocess, hostname, status, login_time, last_batch, open_tran,SQLStatement.text
FROM sysprocesses WITH(NOLOCK)
OUTER APPLY fn_get_sql(sql_Handle) SQLStatement
WHERE hostprocess = <ABL Client PID from windows task manager>

The MS SQL Server profiler does not show the CREATE PROCEDURE ... statement when the GUI client PID is profiled

The MS SQL Server profiler shows the PROCEDURE is executed as:



declare @p2 bigint
set @p2=3045
exec dbo._SEQP_nextcustnum 1,@p2 output
select @p2
declare @p2 bigint
set @p2=3050
exec dbo._SEQP_nextcustnum 1,@p2 output
select @p2
exec sp_execute 1,3050,'USA','test','','','','','','','','',1500.00,0,'Net30',0,'','','',NULL

In the above:

The first one shows the current value for the squence table.
The second one shows the sequence value to be inserted for the new record.
The third one is the inserting customer record on the customer table for create customer ABL.

FACT(s) (Environment):

Windows
MS SQL DataServer
OpenEdge 10.x

FIX:

It is expected to show the CREATE PROCEDURE _SEQP_nextcustnum... on the SQLStatement.text column of sysprocess table when a MS SQL server stored procedure is executed on the MS SQL server database. This does not mean the PROCEDURE is created.

FIX:

Ignore the CREATE PROCEDURE _SEQP_nextcustnum... statement SQLStatement.text column of sysprocess table from MS SQL Server