So i add the record in EM, and go to next line. It is there. I execute a select * and it is gone. Than i add a next record and the seed goes up again, like the first record is tehre.
Okay, let us say you have the max seed value of 1000.
1000 12:48
you do an insert. SQL Server 'grabs' the next number - 1001 and holds it ready for the input.
1001 'locked for new data'
But now the insert doesn't happen. It's rolled back, not committed, you cancel it, whatever. SQL Server will not release that number. It's used. Then you redo the insert, SQL Server now grabs the next number - 1002. And you get what appears to be an incorrect/missing value.
there was a trigger on there that was not formed correctly, so as Bill said, the transaction was rolled back.
What is weird was that, it is an on Insert trigger, and i changed it to an on Delete trigger and the inserttransaction was still rolled back. Once i deleted the trigger, it worked fine.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.