Forum Discussion
Arithmetic overflow error converting IDENTITY to data type bigint
Hello SQL experts, I have a legacy application developed when SQL server did not have native support for sequences. So what is does is creates table and uses its primary key as a sequence value gene...
You're reseeding the table to value : 9,223,372,036,854,775,805
Max BIGINT value is: 9,223,372,036,854,775,807
If you run your repro twice, you'll get the Arithmetic overflow error. I'm not even sure why you're doing that to begin with. I think you're intention is to rerun the same test over and over, so please remove the 92233... from the DBCC CHECKIDENT() .
Max BIGINT value is: 9,223,372,036,854,775,807
If you run your repro twice, you'll get the Arithmetic overflow error. I'm not even sure why you're doing that to begin with. I think you're intention is to rerun the same test over and over, so please remove the 92233... from the DBCC CHECKIDENT() .
gyvkoff We are adding Java BigInteger support and hence we need underlying database to support this. Oracle supports this and has no issue. I assuming SQL Server's BIGINT is equivalent to Java's BigInteger data type.