2 replies to this topic

[lastenia_rojas]

Running ProIV 5.5r518 on Windows2000, and MSSQL 2000 with latest service pack:

We intend to port a ProIV app from Oracle to MSSQL. We are currently running small ProIV functions to get a taste of the differences between the two. An issue we've found is that when we do a lscall to a ls that writes to a child table, ProIV is committing the new child records before the function completes (hence there is the possibility of ending up with orphan records if the function rollbacks after the lscall that writes the children). I suspect an incorrect pro4.ini setup is what is causing this behaviour. We are not issuing our own commits nor enabling &#@SUPP-COMM. Currently, the MSSQL database is set as the default SQL database, and we also have the following environment values defined:

SQL_CURSORS=32
SQLSERVE_SELECT_FOR_UPDATE=TRUE
SQL_TRANSACTION_ERROR=Y

We also look at a SQL trace produced by ProIV (TRACESQL=15) and confirmed that ProIV is indeed instructing MSSQL to commit the child records.

Are we missing something?

Any pointers are appreciated. Thanks!.

[Joseph Bove]

lastenia_rojas,

Do you have the iteration count set at all in the LSCALL?

The iteration count will trigger a commit after every X records...

We have applications that run on both Oracle and SQL Server. When I have more time, I'll try to comment on some of the issues that we've seen.

hth,

Joseph

[lastenia_rojas]

Joseph,

Thanks for your reply. Iteration count is not set.

It'd be great if you have the chance to comment on the issues you've seen.