To achieve multi-user concurrency control, Oracle and SQL Server use different strategies to lock records and tables during ispec and report transactions. This can lead to different behavior regarding related to record locks resulting in the queuing of some user transactions and the occurrence of deadlocks.

Using Oracle, it is quite practical to have long-running reports that perform many database reads and updates and that run as a single transaction without affecting other online ispec and report transactions.

However, using SQL Server, the same report can result in record and table locks. This results in blocking other transactions and causing the reports to be queued waiting for long report transactions to complete.

Generally, the solution to this is to break the execution of long reports into multiple transactions by using the Sleep and/or Critical Point commands at strategic points during report execution. This results in a database commit that commits any updates done to that point and releases all records and table locks. Thus, in general SQL Server works better with shorter transactions.

Therefore, while migrating EAE on Oracle to AB Suite (SQL Server), you must check if any reports use the long-running transactions technique and make appropriate modifications to the LDL logic, if required.