1 of 1 people found this helpful
I think LDSD uses SQL sequences to avoid exactly this sort of issue. I'm reasonable sure LDSD doesn't have a staging table where it pops things until the process has been saved. Perhaps a swift call to support would be in order, especially if you can reproduce it.
Thanks Dave, I'll get onto them now
This is down to how the IDENTITY feature works in SQL Server. If you get an ID assigned as part of a transaction but then for some reason that transaction gets rolled back (ie. a truncation error) then the ID does not also roll back. This is because another transaction might have started after the doomed one and already picked the next number by the time the first transaction rolls back.
Unfortunately the only solution is to ensure that there won't be any errors that cause the SQL transaction to fail.
Thanks Stu - I'll put in a recommendation to get rid of certain users then that keep doing this, cause obviously can't be the fault of my lovely attributes