So there is no way of getting this working in SQL server if BIGINT is essentially equivalent to Java's LONG data type with max value 9223372036854775807 ..

• This reply was modified 4 months, 1 week ago by  narwhale.

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...

Thanks. I have already tried using SCOPE_IDENTITY() as well but facing the same error.

Yes, it can go very large. Just for testing big integers we have manually raised the identity value using:

DBCC CHECKIDENT("TempSeqID", RESEED, 9223372036854775805)

• This reply was modified 4 months, 1 week ago by  narwhale.

And accessing it as below:

USE [rcu]
GO

DECLARE @return_value int,
@dNextIndex bigint

EXEC @return_value = [STGSQL].[GetCounter]
@tableName = N'ID',
@dNextIndex = @dNextIndex OUTPUT

SELECT @dNextIndex as N'@dNextIndex'
SELECT 'Return Value' = @return_value

GO

Throws error:

Arithmetic overflow...