Kbase P186685: Why is there PROGRESS_RECID_ALT_ for each table when migrating using computed columns to MS SQL serv
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/27/2011 |
|
Status: Unverified
GOAL:
Why is there PROGRESS_RECID_ALT_ for each table when migrating using computed columns to MS SQL server dataserver?
GOAL:
Can I manually delete column PROGRESS_RECID_ALT_ when using computed columns?
FACT(s) (Environment):
Windows
OpenEdge 10.2B
FIX:
During sub-transaction UNDO logic in ABL block handling, the value of PROGRESS_RECID_ALT_ keeps the value of ROWID as non-NULL temporarily and in those cases the value will be restorative to the integrity.
Previously with the trigger based ROWID solution, the extra update operation in the WRITE trigger served a similar purpose in the trigger ROWID solution before we had a computed column ROWID solution. But its drawbacks were both performance and concurrency. The computed column solution trades in performance and currency problems for the 8 NULL bytes in stored records.
Do not delete this column, or the application will encounter issues.