Order number jumped by 1000

Author	« Topic »
cciknives Advanced Member Canada 225 Posts	Posted - 07/25/2019 : 08:07:21 Would anyone know why order numbers all of a sudden would jump by 1000? Number was 2438 and next order was 3438, etc. We are running SQL database. Thanks, Peter CCI - Tools for the Discriminating Chef Posting update: Interesting, I just checked our USA database and it did the same thing - jumped by 1000 numbers. Edited by - cciknives on 07/25/2019 08:10:08
quadrant Ecommerce Template Guru United Kingdom 1100 Posts	Posted - 07/25/2019 : 08:10:23 Hi Peter, This post may offer some clues: https://www.ecommercetemplates.com/support/topic.asp?TOPIC_ID=109528 Regards, David
dbdave ECT Moderator USA 10289 Posts	Posted - 07/25/2019 : 08:20:51 David is likely spot on there. I am guessing you are on SQL server 2012? That's a bit long in the tooth, so maybe that can be updated. There was a fix servelink put in place years ago for me and if you click through to the original thread there, you will see some info on that.
cciknives Advanced Member Canada 225 Posts	Posted - 07/25/2019 : 08:23:44 Hi Dave, Thanks for the link and advice, it certainly helps explain what might be going on. We upgraded from SQL 2008 to SQL 2017 in the last couple of months so it looks like the same issue may exist in newer versions as well. If no damage, just higher order numbers we can live with that. Regards, Peter CCI - Tools for the Discriminating Chef
dbdave ECT Moderator USA 10289 Posts	Posted - 07/25/2019 : 08:26:43 My comment in the original post stands... quote: Look at it this way, your returning customers will see the new order numbers and say "wow - these folks are really busy" Of course, I would think that's been long fixed, but if Peter with servelink happens to see this, he may know the answer to that.
insight ECT Moderator USA 4476 Posts	Posted - 07/25/2019 : 12:03:15 I don't believe it's anything that will ever be "fixed" as Microsoft don't regard it as an error. For them, it's just a change in default behavior starting around SQL Server 2012 and it's still the same in the SQL Server 2017 versions that we run. You'll see it whenever the database server is rebooted. It would require some considerable reworking of the cart code logic to fit in with Microsoft's world view on this, so it's an impasse really. In response to popular demand (from dbdave mostly ) we made the changes to revert this behavior on our networked SQL Server 2017 installations and have done it on request for dedicated server clients too, so clients hosted here won't see it. If hosted elsewhere your mileage may vary, as will how much of a problem it represents in your case. Peter Professional ecommerce web hosting services Shared hosting Windows & Linux \| Dedicated servers \| Domains \| SSL Ecommerce Templates specialists since 2003 https://servelink.com
dbdave ECT Moderator USA 10289 Posts	Posted - 07/25/2019 : 12:17:00 quote: In response to popular demand (from dbdave mostly [Wink] )
cciknives Advanced Member Canada 225 Posts	Posted - 07/25/2019 : 12:46:02 Thanks Everyone for such fast responses and clarification. I don't think this will be an issue for us to worry about and I think I have my OCD under control over this :) Peter CCI CCI - Tools for the Discriminating Chef
	« Topic »