This is a known issue for SQL Server (not only azure).
I agree that something should be done about it in orders, maybe to add some additional field that will be consisted.
There is no such a task in 3.70 version.
You're right, I'm only bringing up the issue with azure because SQL azure instance bumps happen a lot. This week alone one of the sites I deal with had it happen a dozen times. Perhaps we could add a regular integer field to the order table and add service logic to handle order id creation? If this update brings about a wave of azure installs it's going to become an issue fast.
I agree that something should be done about it in orders, maybe to add some additional field that will be consisted.
There is no such a task in 3.70 version.
You're right, I'm only bringing up the issue with azure because SQL azure instance bumps happen a lot. This week alone one of the sites I deal with had it happen a dozen times. Perhaps we could add a regular integer field to the order table and add service logic to handle order id creation? If this update brings about a wave of azure installs it's going to become an issue fast.
Our developers say that in SQL 2012 you have a certain setting to prevent that. Google this issue for a solution.
