SQL Server
SQL Server
Create a New Table in an Azure Storage Account
See more Azure Table Service Examples
Creates a new table using the Azure Table Service REST API.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
DECLARE @iTmp0 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
-- Implements the following CURL command:
-- curl -X POST \
-- -H "Content-Type: application/json" \
-- -H "Accept: application/json;odata=fullmetadata" \
-- -H "Prefer: return-content" \
-- -d '{
-- "TableName":"mytable"
-- }' https://myaccount.table.core.windows.net/Tables
-- Use the following online tool to generate REST code from a CURL command
-- Convert a cURL Command to REST Source Code
-- IMPORTANT: Make sure to change "myaccount" to your actual Azure Storage Account name.
-- URL: https://myaccount.table.core.windows.net/Tables
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, 'myaccount.table.core.windows.net', @port, @bTls, @bAutoReconnect
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'ConnectFailReason', @iTmp0 OUT
PRINT 'ConnectFailReason: ' + @iTmp0
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
RETURN
END
-- Provide Azure Cloud credentials for the REST call.
DECLARE @azAuth int
EXEC @hr = sp_OACreate 'Chilkat.AuthAzureStorage', @azAuth OUT
EXEC sp_OASetProperty @azAuth, 'AccessKey', 'AZURE_ACCESS_KEY'
-- The account name used here should match the 1st part of the domain passed in the call to Connect (above).
EXEC sp_OASetProperty @azAuth, 'Account', 'myaccount'
EXEC sp_OASetProperty @azAuth, 'Scheme', 'SharedKey'
EXEC sp_OASetProperty @azAuth, 'Service', 'Table'
-- This causes the "x-ms-version: 2019-07-07" header to be automatically added.
EXEC sp_OASetProperty @azAuth, 'XMsVersion', '2019-07-07'
EXEC sp_OAMethod @rest, 'SetAuthAzureStorage', @success OUT, @azAuth
-- Note: The application does not need to explicitly set the following
-- headers: Content-Length, x-ms-date, Authorization. These headers
-- are automatically set by Chilkat.
-- Note: The above code does not need to be repeatedly called for each REST request.
-- The rest object can be setup once, and then many requests can be sent. Chilkat will automatically
-- reconnect within a FullRequest* method as needed. It is only the very first connection that is explicitly
-- made via the Connect method.
-- Use this online tool to generate code from sample JSON:
-- Generate Code to Create JSON
-- The following JSON is sent in the request body.
-- {
-- "TableName": "mytable"
-- }
DECLARE @json int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'TableName', 'mytable'
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Accept', 'application/json;odata=fullmetadata'
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Prefer', 'return-content'
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Content-Type', 'application/json'
DECLARE @sbRequestBody int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbRequestBody OUT
EXEC sp_OAMethod @json, 'EmitSb', @success OUT, @sbRequestBody
DECLARE @sbResponseBody int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbResponseBody OUT
EXEC sp_OAMethod @rest, 'FullRequestSb', @success OUT, 'POST', '/Tables', @sbRequestBody, @sbResponseBody
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @azAuth
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbRequestBody
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 @azAuth
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbRequestBody
EXEC @hr = sp_OADestroy @sbResponseBody
RETURN
END
DECLARE @jsonResponse int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonResponse OUT
EXEC sp_OAMethod @jsonResponse, 'LoadSb', @success OUT, @sbResponseBody
EXEC sp_OASetProperty @jsonResponse, 'EmitCompact', 0
EXEC sp_OAMethod @jsonResponse, 'Emit', @sTmp0 OUT
PRINT @sTmp0
DECLARE @odata_metadata nvarchar(4000)
EXEC sp_OAMethod @jsonResponse, 'StringOf', @odata_metadata OUT, '"odata.metadata"'
DECLARE @odata_type nvarchar(4000)
EXEC sp_OAMethod @jsonResponse, 'StringOf', @odata_type OUT, '"odata.type"'
DECLARE @odata_id nvarchar(4000)
EXEC sp_OAMethod @jsonResponse, 'StringOf', @odata_id OUT, '"odata.id"'
DECLARE @odata_editLink nvarchar(4000)
EXEC sp_OAMethod @jsonResponse, 'StringOf', @odata_editLink OUT, '"odata.editLink"'
DECLARE @TableName nvarchar(4000)
EXEC sp_OAMethod @jsonResponse, 'StringOf', @TableName OUT, 'TableName'
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @azAuth
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbRequestBody
EXEC @hr = sp_OADestroy @sbResponseBody
EXEC @hr = sp_OADestroy @jsonResponse
END
GO