OpenEdge Data Management: DataServer for Microsoft SQL Server

Migration Issues
Modifying your insert trigger
A–4
Progress Version 9.1D modified the insert trigger that it places on a table in the foreign database
when the PROGRESS RECID support is selected. The modification reduces the level of contention
between multiple users performing inserts simultaneously. The reduction in contention can
produce performance improvement.
If your database was created using the OpenEdge DB to MS SQL Server utility and PROGRESS
RECID support is enabled, Progress Software Corporation recommends that you re-create your
database by dumping your data, executing the OpenEdge DB to MS SQL Server migration
again, and then reloading your data. If this is not possible, then you can manually change your
existing MS SQL Server database by doing the following on each table that has been defined
with PROGRESS RECID support from your MS SQL Server Migration:
1. Drop the unique index created over the PROGRESS_RECID field. There should be one index
for each table created during the initial migration. The syntax is:
Syntax
DROP index ..#_#progress_recid.
2. Drop the old insert trigger. The name typically looks like _TI_. The syntax is:
Syntax
DROP trigger .