thbroadbent,
dilyais is correct. I'm only firing insert statments at the table. Have not come accross this problem using other methods (ADO etc), only when I wrap large numbers of insert statements in transactions.
I have found that when I commit after each INSERT statement (not using transactions) the problem dissappears. It will make any process slightly slower but seems to be the only sure way of getting a sequential identity key.
Yes, this happened to me to and none of the above three options were true. In my product INSERT statements are fired at a table and the transaction commited every 10,000 records. I get small jumps (of 2-5) in the identity key. Very annoying! If anyone knows how to fix the I would be very...
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.