(SQL Server) Demonstrates how to Handle Large Integers in JSON

See more JSON Examples

Demonstrates how to handle large integers in JSON. (Integers larger than what can fit in a 32-bit signed integer.)

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- Let's say your JSON has this:

    -- {
    -- 	"id": 20000000001234567
    -- }

    DECLARE @json int
    -- Use "Chilkat_9_5_0.JsonObject" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @success int
    EXEC sp_OAMethod @json, 'LoadFile', @success OUT, 'qa_data/json/large_int.json'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @json, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @json
        RETURN
      END

    -- The integer is too large for a 32-bit signed integer that is returned by IntOf.
    -- The result will be something that wrapped around and could be negative.
    -- In this case it would be: -543893881
    DECLARE @id int
    EXEC sp_OAMethod @json, 'IntOf', @id OUT, 'id'

    PRINT 'id: ' + @id

    -- The solution is to read the integer value as a string, and then use the features in your programming language
    -- to convert from a string to a 64-bit integer.
    -- 
    -- Alternatively, you may wish to simply hold the value as a string.  If, for example, the integer simply references
    -- an order ID, an account ID, etc., then there's no need to convert to an integer value.  You're not going to be doing
    -- mathematical operations on it anyway.  This is usually the case for large integers -- they typically exist
    -- in JSON as an account ID.

    -- You can get any JSON value as a string:
    DECLARE @accountId nvarchar(4000)
    EXEC sp_OAMethod @json, 'StringOf', @accountId OUT, 'id'

    PRINT 'accountId: ' + @accountId

    -- Sample output:

    -- id: -543893881
    -- accountId: 20000000001234567

    EXEC @hr = sp_OADestroy @json


END
GO