(SQL Server) Re-Encode (How to convert encodings)

Demonstrates how to convert a string from one encoding to another.

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
    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

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

    DECLARE @s1 nvarchar(4000)
    SELECT @s1 = 'This is a test / = abc 123'

    -- The ReEncode method converts a string from one encoding
    -- to another.
    -- Valid encodings are "url", "base64", "qp", "hex", "ansi", "modbase64", "base64url", "base32", "base58",
    -- and any of the encodings listed here:  http://cknotes.com/chilkat-binary-encoding-list

    -- Use "ansi" for an unencoded ANSI string.

    -- Encode to URL-encoding:
    DECLARE @s2 nvarchar(4000)
    EXEC sp_OAMethod @crypt, 'ReEncode', @s2 OUT, @s1, 'ansi', 'url'

    PRINT @s2

    -- Convert from URL-encoding to base64:
    DECLARE @b64 nvarchar(4000)

    EXEC sp_OAMethod @crypt, 'ReEncode', @b64 OUT, @s2, 'url', 'base64'

    PRINT @b64

    -- Convert from base64 to hex:
    DECLARE @hex nvarchar(4000)

    EXEC sp_OAMethod @crypt, 'ReEncode', @hex OUT, @b64, 'base64', 'hex'

    PRINT @hex

    EXEC @hr = sp_OADestroy @crypt


END
GO