Azure Storage - Create table
Declaration
<AMAZURESTORAGE ACTIVITY="create_table" TABLE="text" PROTOCOL="text options)" ACCOUNTNAME="text" ACCESSKEY="text (encrypted)" BLOBENDPOINT="text" QUEUEENDPOINT="text" TABLEENDPOINT="text" TIMEOUT="number" PROXYTYPE="text (options)" PROXYSERVER="text" PROXYPORT="number" PROXYUSERNAME="text" PROXYPASSWORD="text (encrypted)" />
Description: Creates a new table under the given account. Tables store data as collections of entities. Tables don't enforce a schema on entities, which means a single table can contain entities that have different sets of properties.
Practical Usage
Used to create structured storage in the form a table.
Connection Parameters
Property | Type | Required | Default | Markup | Description |
---|---|---|---|---|---|
Connection |
|
|
|
|
Indicates where user credentials and preferences should originate from. This is a design mode parameter used only during task construction and configuration, thus, comprises no markup. The available options are:
|
Session |
Text |
Yes if connection is session-based |
AzureStorageSession1 |
SESSION="MyAzureSession" |
The name of an existing session to associate this activity with. This parameter is active only if the Connection parameter is set to Session. The default session name is 'AzureStorageSession1'. |
Account name |
Text |
Yes if connection is host-based |
(Empty) |
ACCOUNTNAME="myaccount" |
The globally unique name of the Windows Azure storage account. This parameter is active only if the Connection parameter is set to Host. |
Access key |
Text |
Yes if connection is host-based |
(Empty) |
ACCESSKEY="[AccessKey]" |
The primary or secondary access key (each composed of 88 ASCII characters) used to authorize access to Azure Storage. This parameter is active only if the Connection parameter is set to Host. |
Protocol |
Text (options) |
No |
HTTPS |
|
The type of protocol used to access Azure Storage. The available options are:
|
Timeout (seconds) |
Number |
No |
90 |
TIMEOUT="180" |
The timeout interval (in seconds) for requests made to the storage service. If the timeout elapses before a server response is returned, the operation times out and the service returns an error. The default timeout value is 90 seconds. |
Blob endpoint URI |
Text |
No |
(Empty) |
BLOBENDPOINT="http:// accnt
.blob.core.windows.net" |
The endpoint for the Blob service, as configured for the Azure Storage account. The default Blob service endpoint is'[http/https]://accountname.blob.core.windows.net',where 'accountname' is the name of the Azure Storage account. |
Queue endpoint URI |
Text |
No |
(Empty) |
QUEUEENDPOINT="http:// accnt
.queue.core.windows.net" |
The endpoint for the Queue service, as configured for the Azure storage account. The default Queue service endpoint is '[http/https]://accountname.queue.core.windows.net' , where 'accountname' is the name of the Azure Storage account. |
Table endpoint URI |
Text |
No |
(Empty) |
TABLEENDPOINT="http:// accnt
.table.core.windows.net" |
The endpoint for the Table service, as configured for the Azure storage account. The default Table service endpoint is ' Property |
Table name |
Text |
Yes |
(Empty) |
TABLE="mytable" |
The unique name of the table to be created. Table names preserve the case with which they were created, but are case-insensitive when used. Table names must conform to the following rules:
|
Description tab - A custom description can be provided on the Description tab to convey additional information or share special notes about a task step.
Error Causes tab - Specify how this step should behave upon the occurrence of an error. (Refer to Task Builder > Error Causes Tab for details.)
On Error tab - Specify what AWE should do if this step encounters an error as defined on the Error Causes tab. (Refer to Task Builder > On Error Tab for details.)
Example
The sample AML code below can be copied and pasted directly into the Steps panel of the Task Builder.
Description: A simple Azure Storage session that creates a new table and inserts entities into a specific partition/row of the table. It also uploads entities retrieved from a .csv file onto a new table.
<!--Create session --> <AMAZURESTORAGE ACTIVITY="create_session" ACCOUNTNAME="netauto" ACCESSKEY="AM3iiVi4GlX+AHmMoxmR8X662rS FHWxHn0abTRBWBxM2ZIJQ2QFrQapQE6+qUP/Islta6nfcdHj0SfNj+fWwskg 8Q==aME" PROTOCOL="http" SESSION="AzureStorageSession1" /> <!-- Create table --> <AMAZURESTORAGE ACTIVITY="create_table" SESSION="AzureStorageSession1" TABLE="customerBase" /> <!-- Insert entity --><AMAZURESTORAGE ACTIVITY="insert_entity" SESSION="AzureStorageSession1" TABLE="customerBase" PARTITIONKEY="2" ROWKEY="3"><PROPERTY NAME="Name" TYPE="string" VALUE="David" /></AMAZURESTORAGE> <!-- Upload entity --> <AMAZURESTORAGE ACTIVITY="upload_entities" SESSION="AzureStorageSession1" TABLE="SupportBase" FILE="C:\Temp\Support.csv" /><!-- End Session --> <AMAZURESTORAGE ACTIVITY="end_session" />