June 16, 2026 at 12:56 pm
Ask him for the code to reproduce the problem.
Also ask whether the server was restarted between inserts.
June 16, 2026 at 1:20 pm
and its possible that someone did a insert with a high value and used identity insert - that would set the identity value to that of the insert
June 16, 2026 at 4:34 pm
Since the jump was 10000, the datatype is presumably bigint (int cache size is 1000).
June 16, 2026 at 5:34 pm
yes, i believe he uses bigint as his pk's. do you think that has something to do with this?
June 16, 2026 at 10:01 pm
yes, i believe he uses bigint as his pk's. do you think that has something to do with this?
No, that's just the behavior. An int column would have jumped by 1000.
Is there a process that is constantly failing or rolling back transactions?
No server failures. Was SQL Server service restarted? AG failover?
Unless the table has exhausted values -- and it's a bigint, so that's impossible unless server blips constantly (Nobody is storing 18 quintillion rows in SQL Server... or any RDBMS).
How many rows are inserted per day?
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply