Table storage basics in Azure - Mini Project: Build & Apply

Table storage basics

📖 Scenario: You are working on a simple cloud app that needs to store user information in a table format. Azure Table Storage is a good choice for this because it stores data in tables with rows and columns, like a spreadsheet.Imagine you want to keep track of users with their unique IDs, names, and email addresses.

🎯 Goal: Build a basic Azure Table Storage setup by creating a table, adding user data entries, and configuring the table to be ready for queries.

📋 What You'll Learn

Create a table client connected to a storage account

Define a table named 'Users'

Add user entities with PartitionKey, RowKey, Name, and Email

Set up the table to allow querying user data

💡 Why This Matters

🌍 Real World

Azure Table Storage is used to store large amounts of structured, non-relational data. This project shows how to set up and use it for simple user data storage.

💼 Career

Understanding how to create tables, add entities, and query data in Azure Table Storage is essential for cloud developers and engineers working with Microsoft Azure.

1

Create the Azure Table client and define the table name

Write code to create a TableServiceClient using the connection string "DefaultEndpointsProtocol=https;AccountName=examplestorage;AccountKey=examplekey;EndpointSuffix=core.windows.net". Then create a table_client for the table named "Users".

Azure

# Create TableServiceClient and table_client for 'Users' table
# Your code here

Hint

Use TableServiceClient.from_connection_string() with the exact connection string. Then get the table client for the table named "Users".

2

Create the 'Users' table if it does not exist

Add code to create the table named "Users" using the table_client. Use the method create_table() and handle the case where the table might already exist.

Azure

from azure.core.exceptions import ResourceExistsError

# Create the 'Users' table if it does not exist
# Your code here

Hint

Use table_client.create_table() inside a try-except block to catch ResourceExistsError.

3

Add user entities to the 'Users' table

Write code to add two user entities to the table_client. Each entity must have PartitionKey, RowKey, Name, and Email. Use table_client.create_entity() to add these entities. Use these exact values:
1. PartitionKey: "User", RowKey: "001", Name: "Alice", Email: "[e-mail]"
2. PartitionKey: "User", RowKey: "002", Name: "Bob", Email: "[e-mail]"

Azure

# Add two user entities with PartitionKey, RowKey, Name, and Email
# Your code here

Hint

Define two dictionaries with the exact keys and values. Use table_client.create_entity() to add each entity.

4

Query the 'Users' table for all user entities

Add code to query all entities from the table_client using list_entities(). Store the result in a variable called users. This will prepare the table for reading user data.

Azure

# Query all entities from the 'Users' table and store in 'users'
# Your code here

Hint

Use table_client.list_entities() and assign it to users.

Practice

1. What two keys uniquely identify a record in Azure Table Storage?

easy

A. StorageKey and DataKey

B. PrimaryKey and SecondaryKey

C. PartitionKey and RowKey

D. TableKey and RecordKey

Solution

1. Step 1: Understand Azure Table Storage keys

   Azure Table Storage uses two keys to uniquely identify each record: PartitionKey and RowKey.

2. Step 2: Confirm uniqueness of keys

   PartitionKey groups records, and RowKey uniquely identifies a record within that partition.

3. Final Answer:

   PartitionKey and RowKey -> Option C

4. Quick Check:

   Unique record ID = PartitionKey + RowKey [OK]

Hint: Remember: PartitionKey groups, RowKey identifies [OK]

Common Mistakes:

• Confusing PartitionKey with PrimaryKey
• Thinking TableKey is a valid key
• Assuming only one key is needed

2. Which of the following is the correct way to create a table client in Azure SDK for Table Storage?

easy

A. TableClient = new TableServiceClient(tableName).GetTableClient(connectionString);

B. TableClient = new TableClient(tableName, connectionString);

C. TableClient = new TableServiceClient(tableName).GetClient(connectionString);

D. TableClient = new TableClient(connectionString, tableName);

Solution

1. Step 1: Review Azure Table Storage SDK syntax

   The correct constructor for TableClient requires connection string first, then table name.

2. Step 2: Match syntax to options

   TableClient = new TableClient(connectionString, tableName); matches the correct syntax: new TableClient(connectionString, tableName); others mix order or use wrong classes.

3. Final Answer:

   TableClient = new TableClient(connectionString, tableName); -> Option D

4. Quick Check:

   Constructor order: connectionString, tableName [OK]

Hint: Connection string always comes before table name [OK]

Common Mistakes:

• Swapping connection string and table name order
• Using TableServiceClient instead of TableClient
• Calling non-existent methods like GetClient

3. Given this code snippet, what will be the output?

var entity = new TableEntity("users", "user1") { { "Name", "Alice" }, { "Age", 30 } };
Console.WriteLine(entity.PartitionKey + ", " + entity.RowKey + ", " + entity["Name"]);

medium

A. user1, users, Alice

B. users, user1, Alice

C. users, user1, 30

D. user1, users, 30

Solution

1. Step 1: Identify PartitionKey and RowKey values

   PartitionKey is "users" and RowKey is "user1" as set in the constructor.

2. Step 2: Access the "Name" property value

   The "Name" property is set to "Alice", so entity["Name"] returns "Alice".

3. Final Answer:

   users, user1, Alice -> Option B

4. Quick Check:

   PartitionKey, RowKey, Name = users, user1, Alice [OK]

Hint: PartitionKey first, RowKey second, then properties [OK]

Common Mistakes:

• Mixing PartitionKey and RowKey order
• Printing Age instead of Name
• Confusing property access syntax

4. You try to insert an entity with the same PartitionKey and RowKey twice. What will happen?

medium

A. An error occurs because keys must be unique.

B. The table creates a duplicate record with a new key.

C. The second insert overwrites the first entity silently.

D. The insert is ignored without error.

Solution

1. Step 1: Understand uniqueness constraint in Table Storage

   PartitionKey and RowKey together uniquely identify an entity; duplicates are not allowed.

2. Step 2: Behavior on duplicate insert

   Trying to insert an entity with existing keys causes an error, preventing duplicates.

3. Final Answer:

   An error occurs because keys must be unique. -> Option A

4. Quick Check:

   Duplicate keys cause error, no silent overwrite [OK]

Hint: Duplicate keys cause error, not overwrite [OK]

Common Mistakes:

• Assuming silent overwrite happens
• Thinking duplicates are allowed
• Believing insert is ignored silently

5. You want to design a scalable Azure Table Storage schema for a large user database. Which approach best supports fast lookups and scalability?

hard

A. Use PartitionKey as user country and RowKey as user ID

B. Use PartitionKey as user ID and RowKey as timestamp

C. Use a single PartitionKey for all users and RowKey as user ID

D. Use random GUIDs for both PartitionKey and RowKey

Solution

1. Step 1: Understand partitioning for scalability

   PartitionKey groups data to distribute load; grouping by country balances partitions.

2. Step 2: Use RowKey for unique identification

   RowKey as user ID uniquely identifies users within each country partition.

3. Step 3: Evaluate other options

   Single partition causes bottleneck; random GUIDs reduce query efficiency; user ID as PartitionKey fragments data poorly.

4. Final Answer:

   Use PartitionKey as user country and RowKey as user ID -> Option A

5. Quick Check:

   Partition by country, RowKey unique ID = scalable [OK]

Hint: PartitionKey groups data logically for scalability [OK]

Common Mistakes:

• Using single partition for all data
• Random keys hurting query performance
• Misusing RowKey as partitioning key