Quickstart: Build a Table API app with .NET and Azure Cosmos DB
This quickstart shows how to use .NET and the Azure Cosmos DB Table API to build an app by cloning an example from GitHub. This quickstart also shows you how to create an Azure Cosmos DB account and how to use Data Explorer to create tables and entities in the web-based Azure portal.
Azure Cosmos DB is Microsoft’s globally distributed multi-model database service. You can quickly create and query document, key/value, and graph databases, all of which benefit from the global distribution and horizontal scale capabilities at the core of Azure Cosmos DB.
If you don’t already have Visual Studio 2017 installed, you can download and use the free Visual Studio 2017 Community Edition. Make sure that you enable Azure development during the Visual Studio setup.
Create a database account
You must create a new Table API account to work with the generally available Table API SDKs. Table API accounts created during preview are not supported by the generally available SDKs.
- In a new browser window, sign in to the Azure portal.
In the left menu, click Create a resource, click Databases, and then under Azure Cosmos DB, click Create.
In the Create Azure Cosmos DB Account page, enter the settings for the new Azure Cosmos DB account.
Setting Value Description Subscription Your subscription Select the Azure subscription that you want to use for this Azure Cosmos DB account. Resource Group Create new
Then enter the same unique name as provided in ID
Select Create new. Then enter a new resource-group name for your account. For simplicity, use the same name as your ID. Account Name Enter a unique name Enter a unique name to identify your Azure Cosmos DB account. Because documents.azure.com is appended to the ID that you provide to create your URI, use a unique ID.
The ID can use only lowercase letters, numbers, and the hyphen (-) character. It must be between 3 and 31 characters in length.
API Azure Table The API determines the type of account to create. Azure Cosmos DB provides five APIs: Core(SQL) for document databases, Gremlin for graph databases, MongoDB for document databases, Azure Table, and Cassandra. Currently, you must create a separate account for each API.
Select Azure Table because in this quickstart you are creating a table that works with the Table API.
Learn more about the Table API
Location Select the region closest to your users Select a geographic location to host your Azure Cosmos DB account. Use the location that's closest to your users to give them the fastest access to the data.
Select Review+Create. You can skip the Network and Tags section.
The account creation takes a few minutes. Wait for the portal to display the Congratulations! Your Azure Cosmos DB account was created page.
Add a table
You can now use the Data Explorer tool in the Azure portal to create a database and table.
Click Data Explorer > New Table.
The Add Table area is displayed on the far right, you may need to scroll right to see it.
In the Add Table page, enter the settings for the new table.
Setting Suggested value Description Table Id sample-table The ID for your new table. Table names have the same character requirements as database ids. Database names must be between 1 and 255 characters, and cannot contain
/ \ # ?or a trailing space.
Storage capacity Fixed (10 GB) Use the default value of Fixed (10 GB). This value is the storage capacity of the database. Throughput 400 RUs Change the throughput to 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later.
Data Explorer displays the new database and table.
Add sample data
You can now add data to your new table using Data Explorer.
In Data Explorer, expand sample-table, click Entities, and then click Add Entity.
Now add data to the PartitionKey value box and RowKey value box, and click Add Entity.
You can now add more entities to your table, edit your entities, or query your data in Data Explorer. Data Explorer is also where you can scale your throughput and add stored procedures, user-defined functions, and triggers to your table.
Clone the sample application
Now let's clone a Table app from GitHub, set the connection string, and run it. You'll see how easy it is to work with data programmatically.
Open a command prompt, create a new folder named git-samples, then close the command prompt.
Open a git terminal window, such as git bash, and use the
cdcommand to change to the new folder to install the sample app.
Run the following command to clone the sample repository. This command creates a copy of the sample app on your computer.
git clone https://github.com/Azure-Samples/storage-table-dotnet-getting-started.git
Open the sample application in Visual Studio
In Visual Studio, from the File menu, choose Open, then choose Project/Solution.
Navigate to the folder where you cloned the sample application, and open the TableStorage.sln file.
Update your connection string
Now go back to the Azure portal to get your connection string information and copy it into the app. This enables your app to communicate with your hosted database.
In the Azure portal, click Connection String.
Use the copy button on the right side of the window to copy the PRIMARY CONNECTION STRING.
In Visual Studio, open the App.config file.
Uncomment the StorageConnectionString on line 8 and comment out the StorageConnectionString on line 7, because this tutorial does not use the Azure SDK Storage Emulator. Lines 7 and 8 should now look like this:
<!--key="StorageConnectionString" value="UseDevelopmentStorage=true;" />--> <add key="StorageConnectionString" value="DefaultEndpointsProtocol=https;AccountName=[AccountName];AccountKey=[AccountKey]" />
Paste the PRIMARY CONNECTION STRING from the portal into the StorageConnectionString value on line 8. Paste the string inside the quotes.
If your Endpoint uses documents.azure.com, that means you have a preview account, and you must create a new Table API account to work with the generally available Table API SDK.
Line 8 should now appear similar to:
<add key="StorageConnectionString" value="DefaultEndpointsProtocol=https;AccountName=<account name>;AccountKey=<account-key>;TableEndpoint=https://<account name>.table.cosmosdb.azure.com;" />
Press CTRL+S to save the App.config file.
You've now updated your app with all the info it needs to communicate with Azure Cosmos DB.
Build and deploy the app
In Visual Studio, right-click on the TableStorage project in Solution Explorer and then click Manage NuGet Packages.
In the NuGet Browse box, type Microsoft.Azure.CosmosDB.Table. This will find the Cosmos DB Table API client library. Note that this library is currently available for .NET Standard only, it's not yet available for .NET Core.
Click Install to install the Microsoft.Azure.CosmosDB.Table library. This installs the Azure Cosmos DB Table API package and all dependencies.
Open BasicSamples.cs. Right-click on line 52, select Breakpoint, then select Insert Breakpoint. Insert another breakpoint on line 55.
Press F5 to run the application.
The console window displays the name of the new table database (in this case, demo91ab4) in Azure Cosmos DB.
If you get an error about dependencies, see Troubleshooting.
When you hit the first breakpoint, go back to Data Explorer in the Azure portal. Click the Refresh button, expand the demo* table, and click Entities. The Entities tab on the right shows the new entity that was added for Walter Harp. Note that the phone number for the new entity is 425-555-0101.
Close the Entities tab in Data Explorer.
Press F5 to run the app to the next breakpoint.
When you hit the breakpoint, switch back to the Azure portal, click Entities again to open the Entities tab, and note that the phone number has been updated to 425-555-0105.
Press F5 to run the app.
The app adds entities for use in an advanced sample app that the Table API currently does not support. The app then deletes the table created by the sample app.
In the console window, press Enter to end the execution of the app.
Review SLAs in the Azure portal
The throughput, storage, availability, latency, and consistency of the resources in your account are monitored in the Azure portal. Let's take a quick look at these metrics.
Click Metrics in the navigation menu.
Click through each of the tabs so you're aware of the metrics Azure Cosmos DB provides.
Each chart that's associated with the Azure Cosmos DB Service Level Agreements (SLAs) provides a line that shows if any of the SLAs have been violated. Azure Cosmos DB makes monitoring your SLAs transparent with this suite of metrics.
Clean up resources
If you're not going to continue to use this app, delete all resources created by this quickstart with the following steps so you don't incur any charges:
In the Azure portal, select Resource groups on the far left, and then select the resource group you created.
If the left menu is collapsed, click to expand it.
In the new window select the resource group, and then click Delete resource group.
In the new window, type the name of the resource group to delete, and then click Delete.
In this quickstart, you've learned how to create an Azure Cosmos DB account, create a table using the Data Explorer, and run an app. Now you can query your data using the Table API.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.