Order number sequence changes after migration

1 week ago
Hi,

Hope somebody could help me with a small issue I have found with my nopCommerce v4.0 store, after migrating the site to a new windows server, i've noticed any new orders taken on the site the order sequence has changed see images below, instead of the next order ID being 20682  following after 20681 it is 21681 adding an extra 1 after the first digit, I noticed in the database the order number is taken from the table row, can this be changed so the sequence can go back to what it was before?







Many thanks again for all your support
1 week ago
Hi, read this post

https://www.nopcommerce.com/en/boards/topic/60425/1000-record-increase-in-order-number-sequence

bye
1 week ago
Many thanks Kava for the suggestion, the site is running on Windows Server 2012, followed the SQL Query against the afFected DB but get the following error, any ideas?

1 week ago
IDENTITY_CACHE wasn’t released until SQL2017.

https://www.mssqltips.com/sqlservertip/5246/sql-server-2017-identitycache-feature/
1 week ago
Thanks for your suggestions, so going back to my initial issue, it seems not to be IDENTITY_CACHE since this only applies to later release of Windows server, any ideas what the problem could be affecting the order numbering?

Many thanks
1 week ago
I seem to remember some similar from a few years ago, and I’m positive it happened to one of my clients.

However, you could spend hours trying to find the cause, but in reality, it doesn’t cause any issues, so you’re wasting your time really :)
1 week ago
SQL Server 2017 introduced a new database scoped configuration option IDENTITY_CACHE.
However, the problem of cached sequence I think goes back to SQL Server 2012.