Dear experts,
For past few weeks , client experience AX 2009 application slowness ,freezes and not allow to login to users in some intervals only . Post some analysis, it has been noticed that always SQL database had dead blocks as follows ,which is related to number sequence table.
SELECT TOP 1 A.NUMBERSEQUENCE, A.TXT, A.LATESTCLEANDATETIME, A.LATESTCLEANDATETIMETZID, A.LOWEST, A.HIGHEST, A.NEXTREC, A.BLOCKED, A.FORMAT, A.CONTINUOUS, A.CYCLIC, A.CLEANATACCESS, A.INUSE, A.NOINCREMENT, A.CLEANINTERVAL, A.DEL_LATESTCLEANDATE, A.DEL_LATESTCLEANTIME, A.ALLOWCHANGEUP, A.ALLOWCHANGEDOWN, A.MANUAL, A.FETCHAHEADQTY, A.FETCHAHEAD, A.MODIFIEDTRANSACTIONID, A.RECVERSION, A.RECID
FROM NUMBERSEQUENCETABLE A WITH ( UPDLOCK) WHERE ((DATAAREAID=@P1) AND (NUMBERSEQUENCE=@P2)) )
In this blog , it quoted as Continuous number sequences might cause this issue and suggested to disable Continuous .
My question is that does MS published any guidelines/best practice which number sequence codes shouldn’t be continuous or share your project/client number sequence configuration experience and how you over come this issue ?
Thanks in advance.
*This post is locked for comments