Question Status

Suggested Answer
Indrachapa Sirimanna asked a question on 21 Mar 2013 1:18 AM

Dear All,

 We are experiencing issues number sequence blocking very oftenly.

When we checked the count of continuous number sequences, it is around 3459

Total number sequence count is 5768. Therefore approximately 60% of the number sequences are setup as continuous. Is this the problem for the number sequence blocking.

Kindly please give me an idea about this.

 

Thanks in advance,

Indrachapa

Reply
Suggested Answer
Martin Dráb responded on 21 Mar 2013 3:34 AM

It surely has impact on blocking, because AX has to go to database every time when a new number is requested. If you use a non-continuous sequence, you can preallocate several numbers and keep them in memory, which limits the number of request to database. Less round trips also means better performance even if no blocking occurs.

If you can use non-continuous sequence, do it.

Martin "Goshoom" Dráb | Freelancer | Goshoom.NET Dev Blog

Reply
Suggested Answer
Tommy Skaue responded on 21 Mar 2013 7:04 AM

Keep the number of continuous number sequences to a bare minimum. Just as Martin explains, there is a performance impact, and it grows quickly out of control and stalls your AX. Just have a look at locking or table/index scans on the table NUMBERSEQUENCELIST on a busy day. Too many customers think all their number sequences needs to be continuous, when they really do not need to be. Normally the only ones needing to be continuous are those related to ledger transactions (not the journal headers, but the vouchers).

Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no

Reply
Suggested Answer
Martin Dráb responded on 21 Mar 2013 3:34 AM

It surely has impact on blocking, because AX has to go to database every time when a new number is requested. If you use a non-continuous sequence, you can preallocate several numbers and keep them in memory, which limits the number of request to database. Less round trips also means better performance even if no blocking occurs.

If you can use non-continuous sequence, do it.

Martin "Goshoom" Dráb | Freelancer | Goshoom.NET Dev Blog

Reply
Suggested Answer
Tommy Skaue responded on 21 Mar 2013 7:04 AM

Keep the number of continuous number sequences to a bare minimum. Just as Martin explains, there is a performance impact, and it grows quickly out of control and stalls your AX. Just have a look at locking or table/index scans on the table NUMBERSEQUENCELIST on a busy day. Too many customers think all their number sequences needs to be continuous, when they really do not need to be. Normally the only ones needing to be continuous are those related to ledger transactions (not the journal headers, but the vouchers).

Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no

Reply
Indrachapa Sirimanna responded on 21 Mar 2013 9:38 PM

Dear Martin,

Thanks for the answer. I think we need to rethink about number sequence setup.

Thanks again,

Indrachapa

Reply
Indrachapa Sirimanna responded on 21 Mar 2013 9:41 PM

Dear Tommy,

As you said, the users are thinking that it's better to have the number sequence as continuous. So they have setup continuous unnecessarily.

Thanks for your feedback.

Regards,

Indrachapa.

Reply