SQL Server
SQL Server
Amazon Glacier Upload Archive from In-Memory Data
See more Amazon Glacier Examples
Demonstrates how to add an archive to a vault from data in memory.Note: This example requires Chilkat v9.5.0.78 or greater.
Chilkat SQL Server Downloads
-- 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 @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
DECLARE @rest int
EXEC @hr = sp_OACreate 'Chilkat.Rest', @rest OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Connect to the Amazon AWS REST server in the desired region.
DECLARE @bTls int
SELECT @bTls = 1
DECLARE @port int
SELECT @port = 443
DECLARE @bAutoReconnect int
SELECT @bAutoReconnect = 1
EXEC sp_OAMethod @rest, 'Connect', @success OUT, 'glacier.us-west-2.amazonaws.com', @port, @bTls, @bAutoReconnect
-- Provide AWS credentials.
DECLARE @authAws int
EXEC @hr = sp_OACreate 'Chilkat.AuthAws', @authAws OUT
EXEC sp_OASetProperty @authAws, 'AccessKey', 'AWS_ACCESS_KEY'
EXEC sp_OASetProperty @authAws, 'SecretKey', 'AWS_SECRET_KEY'
EXEC sp_OASetProperty @authAws, 'ServiceName', 'glacier'
EXEC sp_OASetProperty @authAws, 'Region', 'us-west-2'
EXEC sp_OAMethod @rest, 'SetAuthAws', @success OUT, @authAws
-- --------------------------------------------------------------------------
-- Note: The above REST connection and setup of the AWS credentials
-- can be done once. After connecting, any number of REST calls can be made.
-- The "auto reconnect" property passed to rest.Connect indicates that if
-- the connection is lost, a REST method call will automatically reconnect
-- if needed.
-- --------------------------------------------------------------------------
-- Load the data to be uploaded.
DECLARE @bd int
EXEC @hr = sp_OACreate 'Chilkat.BinData', @bd OUT
EXEC sp_OAMethod @bd, 'LoadFile', @success OUT, 'qa_data/jpg/penguins.jpg'
-- (The point here is that the contents of the bd don't necessarily have to come from a file.)
--
-- For more information, see Glacier Upload Archive Reference Documentation
--
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'x-amz-glacier-version', '2012-06-01'
-- We'll need to pre-compute the SHA256 tree hash and the SHA256 linear hash.
-- The hashes are added in the following request headers:
-- x-amz-sha256-tree-hash: SHA256 tree hash
-- x-amz-content-sha256: SHA256 linear hash
DECLARE @crypt int
EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT
EXEC sp_OASetProperty @crypt, 'HashAlgorithm', 'sha256-tree-hash'
EXEC sp_OASetProperty @crypt, 'EncodingMode', 'hexlower'
DECLARE @treeHashHex nvarchar(4000)
EXEC sp_OAMethod @crypt, 'HashBdENC', @treeHashHex OUT, @bd
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'x-amz-sha256-tree-hash', @treeHashHex
EXEC sp_OASetProperty @crypt, 'HashAlgorithm', 'sha256'
DECLARE @linearHashHex nvarchar(4000)
EXEC sp_OAMethod @crypt, 'HashBdENC', @linearHashHex OUT, @bd
EXEC sp_OASetProperty @authAws, 'PrecomputedSha256', @linearHashHex
-- We can optionally add a description
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'x-amz-archive-description', 'Penguins JPG'
DECLARE @sbResponseBody int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbResponseBody OUT
EXEC sp_OAMethod @rest, 'FullRequestBd', @success OUT, 'POST', '/AWS_ACCOUNT_ID/vaults/chilkat/archives', @bd, @sbResponseBody
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @authAws
EXEC @hr = sp_OADestroy @bd
EXEC @hr = sp_OADestroy @crypt
EXEC @hr = sp_OADestroy @sbResponseBody
RETURN
END
DECLARE @respStatusCode int
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @respStatusCode OUT
IF @respStatusCode >= 400
BEGIN
PRINT 'Response Status Code = ' + @respStatusCode
PRINT 'Response Header:'
EXEC sp_OAGetProperty @rest, 'ResponseHeader', @sTmp0 OUT
PRINT @sTmp0
PRINT 'Response Body:'
EXEC sp_OAMethod @sbResponseBody, 'GetAsString', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @authAws
EXEC @hr = sp_OADestroy @bd
EXEC @hr = sp_OADestroy @crypt
EXEC @hr = sp_OADestroy @sbResponseBody
RETURN
END
-- Success is indicated by a 201 response status with an empty response body.
PRINT 'response status code = ' + @respStatusCode
-- If successful, the response header looks like this.
-- The Location and x-amz-archive-id are two items of information we may wish to save..
-- HTTP/1.1 201 Created
-- x-amzn-RequestId: AAABZpJrTyioDC_HsOmHae8EZp_uBSJr6cnGOLKp_XJCl-Q
-- Date: Wed, 10 Feb 2017 12:00:00 GMT
-- x-amz-sha256-tree-hash: beb0fe31a1c7ca8c6c04d574ea906e3f97b31fdca7571defb5b44dca89b5af60
-- Location: /111122223333/vaults/examplevault/archives/NkbByEejwEggmBz2fTH ... GlqrEXAMPLEArchiveId
-- x-amz-archive-id: NkbByEejwEggmBz2fTHgJrg0XBoDfjP4q6iu87-TjhqG6eGoOY9Z8i1_AUyUsu ... BfGlqrEXAMPLEArchiveId
--
DECLARE @archiveId nvarchar(4000)
EXEC sp_OAMethod @rest, 'ResponseHdrByName', @archiveId OUT, 'x-amz-archive-id'
PRINT 'x-amz-archive-id = ' + @archiveId
DECLARE @location nvarchar(4000)
EXEC sp_OAMethod @rest, 'ResponseHdrByName', @location OUT, 'Location'
PRINT 'Location = ' + @location
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @authAws
EXEC @hr = sp_OADestroy @bd
EXEC @hr = sp_OADestroy @crypt
EXEC @hr = sp_OADestroy @sbResponseBody
END
GO