New programming standards in regards to OCC

[gb]

Hi,

does anybody know if MS released any white paper type document on new standards for programming in X++ regarding OCC ( Optimistic Concurrency )?

What has to be changed with SP5 for 3.0 release? And what needs to be changed with 4.0 upgrade?

I would appreciate any comments.
Thanks,
gb

[gl00mie]

Цитата:

Сообщение от gb

does anybody know if MS released any white paper type document on new standards for programming in X++ regarding OCC (Optimistic Concurrency )?

Afaik there are no official white papers on this topic. Google doesn't know any either.

Цитата:

What has to be changed with SP5 for 3.0 release? And what needs to be changed with 4.0 upgrade?

As I understand OCC should be taken into consideration by DBAs rather then X++ programmers as Axapta kernel takes care about making OCC usage transparent for a developer. Let me translate a part of an article by Alexei Eremenko on OCC support in DAX 3.0/4.0

Цитата:

Optimistic Concurrency Control (OCC) mechanism support has been introduced in Axapta 3.0 Kernel Rollup. Strictly speaking OCC is used in KR only in form data sources while leaving unoptimized other areas that cause database requests. The RecVersion field is used in KR to support OCC, namely to support record versions. Within Dynamics AX the OCC model implemented in 4.0 consists of these parts:

• Hints like 'forupdate' are deleted (excluded) from X++ source code on a kernel level;
• When one or several rows of a record are updated, a check is performed to see if the record has been changed since the time it had been read in the transaction. In case it has been changed an exception is thrown by the kernel (Exception::UpdateConflict);
• X++ code is changed to support such exceptions in try/catch handlers.

OCC assumes optimistic and pessimistic scenarios (see SQL Books online). The pessimistic one is much like what was implemented in Axapta 3.0 before Kernel Rollup. OCC can work in one of these ways in Axapta 4.0:

• Optimistic for those tables where it's explicitly set;
• Optimistic for all tables;
• Pessimistic.

You can also use READ UNCOMMITED isolation level for all read requests. For an optimal OCC support you need to turn on Read Committed Snapshot Isolation (RCSI) isolation level in SQL Server 2005, e.g. this way:

PHP код:

ALTER DATABASE <Microsoft Dynamics Ax database>
SET READ_COMMITTED_SNAPSHOT ON; 


This isolation level is turned off by default which makes SQL Server 2005 fully compatible with pervious versions although you can turn it on even in the compatibility mode, i.e. for the compatibility level 80 databases. People often ask if READ_COMMITTED_SNAPSHOT can improve DAX 3.0 performance. Well in fact DAX 3.0 doesn't support Read Committed Snapshot Isolation (RCSI) in SQL Server 2005.
Here is a presentation on SQL Server 2005 performance improvements that can give you more details on RCSI.