(SQL Server) JSON UpdateNumber vs UpdateInt

Demonstrates UpdateNumber vs UpdateString.

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

    -- If a number is too large for a 32-bit signed integer, then call UpdateNumber instead of UpdateInt.
    -- The large integer is passed to UpdateNumber as a string, but in the JSON it will be an integer.

    -- For example:
    DECLARE @success int
    EXEC sp_OAMethod @json, 'UpdateNumber', @success OUT, 'largeNumber', '6884556842'

    -- If the integer is small enough for a 32-bit signed integer, then use UpdateInt:
    EXEC sp_OAMethod @json, 'UpdateInt', @success OUT, 'reasonableInt', 123456

    EXEC sp_OASetProperty @json, 'EmitCompact', 0
    EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
    PRINT @sTmp0

    -- The output:
    -- Notice the large number passed as a string does not have quotes in the JSON

    -- {
    --   "largeNumber": 6884556842,
    --   "reasonableInt": 123456
    -- }

    EXEC @hr = sp_OADestroy @json


END
GO