(SQL Server) JSON Hex Encoding

See more JSON Examples

Let's say your JSON contains content that is hex encoded like this: \u05d1\u05d3\u05d9\u05e7

This example shows how to get the decoded string.

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 @s nvarchar(4000)
    SELECT @s = '{ "example": "\u05d1\u05d3\u05d9\u05e7" }'

    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, 'Load', @success OUT, @s

    -- When getting the member data, it is automatically decoded.

    EXEC sp_OAMethod @json, 'StringOf', @sTmp0 OUT, 'example'
    PRINT 'member data: ' + @sTmp0

    -- Output:
    -- member data: בדיק

    -- When getting the full JSON, it remains encoded. This is expected and intentional.

    EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
    PRINT 'full JSON: ' + @sTmp0

    -- Output:
    -- full JSON: {"example":"\u05d1\u05d3\u05d9\u05e7"}

    -- To get the full JSON without the encoding, you can decode manually.
    DECLARE @sb int
    -- Use "Chilkat_9_5_0.StringBuilder" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sb OUT

    EXEC sp_OAMethod @json, 'EmitSb', @success OUT, @sb
    -- The hex encoding used by JSON is utf-8.
    EXEC sp_OAMethod @sb, 'Decode', @success OUT, 'json', 'utf-8'

    EXEC sp_OAMethod @sb, 'GetAsString', @sTmp0 OUT
    PRINT @sTmp0

    -- Output:
    -- {"example":"בדיק"}

    EXEC @hr = sp_OADestroy @json
    EXEC @hr = sp_OADestroy @sb


END
GO