SQL Server

Re-Encode (How to convert encodings)

See more Encryption Examples

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

-- 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
    EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Here are some bytes as a hex string
    DECLARE @hex nvarchar(4000)
    SELECT @hex = '4142434445462140232425'

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

    -- Convert from hex to base64
    DECLARE @b64 nvarchar(4000)
    EXEC sp_OAMethod @crypt, 'ReEncode', @b64 OUT, @hex, 'hex', 'base64'

    PRINT 'base64: ' + @b64

    -- Convert from base64 to base32
    DECLARE @b32 nvarchar(4000)
    EXEC sp_OAMethod @crypt, 'ReEncode', @b32 OUT, @b64, 'base64', 'base32'

    PRINT 'base32: ' + @b32

    -- Convert from base32 back to hex
    EXEC sp_OAMethod @crypt, 'ReEncode', @hex OUT, @b32, 'base32', 'hex'

    PRINT 'hex: ' + @hex

    EXEC @hr = sp_OADestroy @crypt


END
GO