Working with Stored Procedure in Azure DocumentDB (CosmosDB)

In this blog post we will learn how to create & test Stored Procedure in Azure DocumentDB (CosmosDB).

 Login to Azure Portal & click on New. Search for cosmosDB-















Click on "Azure Cosmos DB".

Click on "Create".



Fill up all details e.g.- CosmosDB ID, API (for this demonstration we will select DocumentDB), Subscription, Resource Group & Location. Click on "Create" button.

After creating cosmos DB ID you can view as below screenshot-


Below are the some important points which we should keep in mind-
1. We can create multiple Databases under one Cosmos DB. 
2. One database can have multiple collections. 
3. One collection can have multiple documents. 
4. Each document have one field as "id" this is primary key for each document. This is also unique under one collection. We can't create multiple documents with same id under one collection.

To create collection and database click on "Add Collection" button.



If you keep storage capacity as "unlimited" than Partition Key is mandatory. You can select fixed option under storage capacity & keep partitionkey blank.

Lets create some document under collection for testing. Select "Document Explorer" option from Cosmos DB panel.



Click on "Create" option in top option bar.


Add value of id field & add other fields for your document. For now we will add below fields-


Click on "Save" option. 

For Creating & Testing Stored Procedure, Azure provides "Script Explorer". In the Cosmos DB panel click on "Script Explorer"-



Select your Database and Collection name & click on "Create Stored Procedure".



Provide "ID" for Stored Procedure. With new Stored Procedure some basic template is provided to check document in collection. You can customize it as per your requirement.

For testing Stored Procedure, scroll to downside of screen to view place to give input parameters for Stored Procedure & view execution result. 

If there are no record found in collection than you will get below result. 


If you have added documents in collection (as we did in earlier steps), you will get below result-


Result will be look like as below-

test{"id":"1","firstName":"Dharam","lastName":"Sikhwal","Company":"Spadeworx","City":"Pune","_rid":"EyMIAKblHwUBAAAAAAAAAA==","_self":"dbs/EyMIAA==/colls/EyMIAKblHwU=/docs/EyMIAKblHwUBAAAAAAAAAA==/","_etag":"\"0000ce00-0000-0000-0000-5961c3b10000\"","_attachments":"attachments/","_ts":1499579312}


I hope you have understood basic concept of Azure DocumentDB, Documents and Stored Procedure. In next blog we will walk you through using DocumentDB Stored Procedure in Azure Logic Apps.

If you have any query please send email on dharam.pal95@gmail.com.



Comments

  1. Unknown22 August 2018 at 05:16

    This was truly awesome. thanks so much for this..!!..Keep Share your informationAzure Online Training Bangalore

    ReplyDelete

Post a Comment

Popular posts from this blog

Serverless Integration design pattern on Azure to handle millions of transactions per second

Image
Recently i was working on one of the integration project where client have following requirements- It should support millions of transactions per second Based on demand/number of requests it should auto-scale. Client don't want to procure huge hardware up-front. It should support multiple applications integration & open for future integrations without any or minimum changes. If any application is down for some time, framework should have in-build retry logic after some configured schedule. We have analyzed below options for this integration framework- 1. Biztalk Server 2. Azure Function, Logic App & Event Hub 3. Third party integration server Every option has its own pros & cons. Based on client requirement analysis with each option we found option 2, Azure Function and Event Hub approach most suitable for this type of integration. Below are the main features which played a key role to select this framework for integration- Azure Function- A...
Read more

Cloud-Neutral Development is the future of IT

Image
Cloud becomes first choice for deployment of applications for most of the companies. Major benefits of cloud is cost, speed, scale & reliability. With the increase in the number of cloud providers, today companies have many choices to pick their deployment cloud provider. Now major question for any organization is which cloud provider they should choose? Generally all cloud provider gives browser-based dashboard that makes it easier for IT professionals and developers to order resources and manage their accounts. Some cloud computing services are also designed to work with REST APIs and a command-line interface (CLI), giving developers multiple options. If you have specific need in your application and some provider provides PaaS service which fulfill maximum of your requirement than you can go for cloud-native development model. In this model you will stick with particular cloud provider. You will not able to move to other cloud provider in future without any or major changes...
Read more