Welcome back to SkillTech’s #DP-900: Microsoft Azure Data Fundamentals series!
In this module, you’ll learn how to provision #non-relational data services in Azure—an essential skill for managing modern, scalable #NoSQL databases.
What you’ll learn in this video:
Step-by-step guide to provisioning Azure Cosmos DB
Key configurations for non-relational services
Understanding global distribution, partitioning, and throughput
Real-world use cases for document, key-value, and graph databases in Azure
This lesson is ideal for:
DP-900 exam candidates
Beginners in Azure data services
IT professionals exploring NoSQL databases in the cloud
Explore our other Courses and Additional Resources on: https://skilltech.club/
In this module, you’ll learn how to provision #non-relational data services in Azure—an essential skill for managing modern, scalable #NoSQL databases.
What you’ll learn in this video:
Step-by-step guide to provisioning Azure Cosmos DB
Key configurations for non-relational services
Understanding global distribution, partitioning, and throughput
Real-world use cases for document, key-value, and graph databases in Azure
This lesson is ideal for:
DP-900 exam candidates
Beginners in Azure data services
IT professionals exploring NoSQL databases in the cloud
Explore our other Courses and Additional Resources on: https://skilltech.club/
Category
🤖
TechTranscript
00:00Now in this video we are going to explore provisioning and deploying non-relational
00:12data services in Azure. We will focus on deploying Azure storage account and Azure
00:18Cosmos DB account in this particular video. During this provisioning and
00:23deploying we also need to understand some configurational properties of this
00:27non-relational data services. We will explore the basic connectivity issues which
00:31are there and we will also talk about the data security, data replication as
00:37well as the high availability of the data which are associated with this kind of
00:40non-relational data services. Now because I want to provision some of the
00:45non-relational data services in Azure, I have logged into my Azure portal. I'm
00:50going to click on create resource and the first thing which I want to deploy is
00:54Azure Cosmos DB account. I'm going to click on this Azure Cosmos DB which will
01:00take me to a page where I have to choose that what kind of API option I want to
01:06select. As we know that Cosmos DB is a multi-model database of Microsoft and I
01:12can use one of the API which is suggested by them. The basic recommended one is
01:17Core SQL and I think I also use this one because my most of the applications where
01:23I'm going to associate Cosmos DB will be based out of .NET Framework, JavaScript,
01:28Python or Java and I prefer this one so I'm going to click on create. The moment I
01:34do this, this is a Cosmos DB account. Remember one Cosmos DB account can have
01:39multiple Cosmos DBs inside that and that you have to provision once the account is
01:44created. While creating the account you have to provide couple of
01:48configurational things in each tab like all the Azure services. This also has
01:52couple of configurations. I'm going to select my subscription and I'm going to
01:56create a new resource group for this particular training so I'm going to create
02:00a resource group called db900RG and then I'm going to click on OK. Once this is
02:07there I need to provide a proper unique name for my Cosmos DB account. Let's say I
02:12am giving a Cosmos DB account that this is going to be Maruti Azure Cosmos ACC which
02:21is a Cosmos account and I'm just using some unique number at the end of this which
02:25is like 55. It can be any number just to make sure that to keep the uniqueness of
02:31this particular name we are keeping it like this. The location for this Cosmos DB
02:36account I want to keep it East US and then they are asking me what kind of
02:40capacity more I want to select. I want to go with serverless model where costing
02:45will be limited or maybe I want to go with the provision throughput where I can
02:50dedicatedly select what kind of throughput I want. They are also having
02:53some configuration based on my subscription that if I want to apply
02:58some free trial discount on this I can do that. I do not want to apply as of now so
03:02I'm just not doing anything in this. I'm selecting do not apply and then I'm
03:07going to click on next. They are asking me if I want to enable geographical
03:12redundancy, multi-region rights and availability zone. Obviously this
03:17configuration is going to allow me to access and deploy my database across
03:21multiple geographical regions and then as we discussed earlier we have a facility
03:26of multi-region rights. It means the multiple copies will be writable. It's not
03:31only read-only copies like SQL server of Azure. I'm not changing anything in this
03:37tabs right now. I'm okay with my default configuration of networking, backup policy,
03:43encryption and all this. So I'm just going with next next next review plus create. The
03:49last page is going to show me that the deployment of this Azure Cosmos DB account
03:53is going to take approximate two minutes of time. I'm going to click on create and
03:58that will start provisioning of this thing. While Azure Cosmos DB account is
04:03under provisioning, I can deploy some other services also and as we know with
04:08Azure Cosmos DB account, I also want you to see Azure storage account. So once this
04:13deployment is in progress, I do not want to touch this. This is going to be there
04:18in this one tab. In the new tab of my browser, I'm going to provision Azure
04:24storage account. So let me just switch to my another tab. I'm going to
04:28click on create resource and I'm selecting the last option which is storage account.
04:33When we go with Azure storage account, this storage account is also having a
04:38facility of storing data in a semi-structured or unstructured way and as we
04:43discussed we have something like blob storage, file storage kind of thing. I'm
04:47selecting that I want the storage account in the same resource group with my
04:51Cosmos DB. The name of the storage account will be Maruti storage account with
04:56some number at the end of that and then the location for this also we are
05:01selecting East US. What kind of performance and what kind of redundancy I
05:05want for storage account, I can change it and according to that this will create
05:10multiple copies of my data locally, geographically or zone specific
05:15replications. I'm selecting GRS right now and I'm also going to enable read access on
05:21that. So it's like this is going to be read access geo-redundant storage and that's
05:26what I'm selecting. We have an optional feature which we can enable disable in
05:31security where you can see that we can enable secure transfer required for rest
05:36API's. For each data which you're going to store inside a storage account, they
05:41will enable rest API's by which you can access the data. If you have stored blob data
05:46or file data, you can enable this thing for that. I am just going with the default
05:51configuration right now. I can also enable Azure Active Directory based
05:55authorization in this. If I check mark this then only certain users of my Azure
06:00Active Directory domain can be associated with the storage account and can have
06:05privileges associated with that. Also there is one important configuration here.
06:10They are asking me that if I want to create a storage account, I want a normal
06:15storage account or I want a data lake generation based Gen 2 storage account.
06:20We will see Gen 2 storage accounts in depth in the next module when I'm going to
06:25associate Azure Synapse kind of Azure data services with this but as of now I'm
06:31keeping it a normal storage account not the Gen 2 one but we can get
06:35hierarchical namespace in the Gen 2 account. You can research on this what is the
06:39difference between Azure storage and Gen 2 storage account actually by yourself but
06:44I'm not selecting Gen 2. I'm creating a normal storage account and then all other
06:48things are fine. I'm not going to change anything in data protection, networking and
06:52tags. We will click on review plus create. If validation is passed you will
06:57observe one thing that storage accounts are not having any fixed cost. You can see it's
07:02not showing me any estimated cost here because the price of the storage account, the
07:07costing of the storage account is actually based on the amount of data which you
07:11store inside that. It also going to impact and associate with the properties like what
07:16kind of replication you are selecting, what kind of backup configuration you have selected
07:22as well as also which kind of excess tire you have selected. So there are so many properties
07:26which can affect and impact on the storage account pricing but we are not getting any estimated
07:32cost here so we are fine with this. I'm going to click on create and this is going to start
07:38the provisioning of my storage account also. While this deployment is getting submitted I'm
07:45just going to check whether my deployment of the Cosmos DB is done or not. Yes it is successfully
07:50completed. If I click on go to resource this is going to show me that my Cosmos DB account
07:56is successfully created and directly it's taking me to a page which is a quick start page where
08:02I can choose a platform and I can create some kind of structure for my Cosmos DB databases
08:09and tables associated with that. But we do not have actual tables. We need to understand
08:14the structure of this because we have something called container here. We'll see that. But
08:19yes this is showing me that my Cosmos DB account is successfully deployed and it is available
08:24in the East US region and it is actually having status online. Same way if I check my storage
08:32account now and if I click on go to resource my storage account is also having a location
08:37East US. The primary and secondary location is also set up automatically here. The primary
08:43is East US, the secondary which is a replicated copy is in West US and both are available right
08:49now. No problem about that. The storage account is giving me options like containers which allows
08:55me to store blob storage, file shares allows me to store files and tables which allows me
09:01to store data in a tabular format as we have discussed in the previous lesson. And then Cosmos
09:06DB is actually going to allow me to store data in a JSON files. We will see and explore this
09:12kind of structure and this kind of data files into that in the next lesson. But this is what
09:18a provisioning about Azure Cosmos DB and Azure storage account. How to deal with this thing
09:24that we are going to see in the next demo. Let's stick to that. Thank you.
09:30So in this video you have seen that how we can provision and deploy relational data services
09:35in Azure. You have provisioned Azure storage account and Azure Cosmos DB account using the
09:41Azure portal.
09:48Azurelly Command אyzztrap theory,난a.
09:52you have proven that is a stack. At that time, click the subscribe button on your
09:55insurance family itself here, your page on your lottery. You have quite a specific
09:57question. But tip, what users do save you over. One, no, actually, use it for the
09:58wellness agency dot com I view this on my website today, look out for the
10:01description and find out all the description. When you start blogging in the next one, you
10:03saidpping online, go Chloe O kr ze and back, kö anterior coal carer, go bulk
10:08so this. That should add a description of a stack in Minecraft storeее Kingdom security,
10:10you have open website with these tools. You have opened website a list ofают
10:13that in books that you can use that it plural. You can use it really hard to override OHOL and this
10:15the process of mine of mine on the partial deeper content THE kehPader and