Ruthie  Bugala

Ruthie Bugala


Azure Application Insights Profiler

Need to collect performance data about your Azure apps while they are running in production? DevDiv Azure Services PM Chuck Weininger shows us how to do that using the Azure Application Insights Profiler.

#profiler #coding #azure

What is GEEK

Buddha Community

Azure Application Insights Profiler
Ron  Cartwright

Ron Cartwright


Getting Started With Azure Event Grid Viewer

In the last article, we had a look at how to start with Azure DevOps: Getting Started With Audit Streaming With Event Grid

In the article, we will go to the next step to create a subscription and use webhook event handlers to view those logs in our Azure web application.

#cloud #tutorial #azure #event driven architecture #realtime #signalr #webhook #azure web services #azure event grid #azure #azure event grid #serverless architecture #application integration

Eric  Bukenya

Eric Bukenya


Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB

This article is a part of the series – Learn NoSQL in Azure where we explore Azure Cosmos DB as a part of the non-relational database system used widely for a variety of applications. Azure Cosmos DB is a part of Microsoft’s serverless databases on Azure which is highly scalable and distributed across all locations that run on Azure. It is offered as a platform as a service (PAAS) from Azure and you can develop databases that have a very high throughput and very low latency. Using Azure Cosmos DB, customers can replicate their data across multiple locations across the globe and also across multiple locations within the same region. This makes Cosmos DB a highly available database service with almost 99.999% availability for reads and writes for multi-region modes and almost 99.99% availability for single-region modes.

In this article, we will focus more on how Azure Cosmos DB works behind the scenes and how can you get started with it using the Azure Portal. We will also explore how Cosmos DB is priced and understand the pricing model in detail.

How Azure Cosmos DB works

As already mentioned, Azure Cosmos DB is a multi-modal NoSQL database service that is geographically distributed across multiple Azure locations. This helps customers to deploy the databases across multiple locations around the globe. This is beneficial as it helps to reduce the read latency when the users use the application.

As you can see in the figure above, Azure Cosmos DB is distributed across the globe. Let’s suppose you have a web application that is hosted in India. In that case, the NoSQL database in India will be considered as the master database for writes and all the other databases can be considered as a read replicas. Whenever new data is generated, it is written to the database in India first and then it is synchronized with the other databases.

Consistency Levels

While maintaining data over multiple regions, the most common challenge is the latency as when the data is made available to the other databases. For example, when data is written to the database in India, users from India will be able to see that data sooner than users from the US. This is due to the latency in synchronization between the two regions. In order to overcome this, there are a few modes that customers can choose from and define how often or how soon they want their data to be made available in the other regions. Azure Cosmos DB offers five levels of consistency which are as follows:

  • Strong
  • Bounded staleness
  • Session
  • Consistent prefix
  • Eventual

In most common NoSQL databases, there are only two levels – Strong and EventualStrong being the most consistent level while Eventual is the least. However, as we move from Strong to Eventual, consistency decreases but availability and throughput increase. This is a trade-off that customers need to decide based on the criticality of their applications. If you want to read in more detail about the consistency levels, the official guide from Microsoft is the easiest to understand. You can refer to it here.

Azure Cosmos DB Pricing Model

Now that we have some idea about working with the NoSQL database – Azure Cosmos DB on Azure, let us try to understand how the database is priced. In order to work with any cloud-based services, it is essential that you have a sound knowledge of how the services are charged, otherwise, you might end up paying something much higher than your expectations.

If you browse to the pricing page of Azure Cosmos DB, you can see that there are two modes in which the database services are billed.

  • Database Operations – Whenever you execute or run queries against your NoSQL database, there are some resources being used. Azure terms these usages in terms of Request Units or RU. The amount of RU consumed per second is aggregated and billed
  • Consumed Storage – As you start storing data in your database, it will take up some space in order to store that data. This storage is billed per the standard SSD-based storage across any Azure locations globally

Let’s learn about this in more detail.

#azure #azure cosmos db #nosql #azure #nosql in azure #azure cosmos db

Ruthie  Bugala

Ruthie Bugala


How to set up Azure Data Sync between Azure SQL databases and on-premises SQL Server

In this article, you learn how to set up Azure Data Sync services. In addition, you will also learn how to create and set up a data sync group between Azure SQL database and on-premises SQL Server.

In this article, you will see:

  • Overview of Azure SQL Data Sync feature
  • Discuss key components
  • Comparison between Azure SQL Data sync with the other Azure Data option
  • Setup Azure SQL Data Sync
  • More…

Azure Data Sync

Azure Data Sync —a synchronization service set up on an Azure SQL Database. This service synchronizes the data across multiple SQL databases. You can set up bi-directional data synchronization where data ingest and egest process happens between the SQL databases—It can be between Azure SQL database and on-premises and/or within the cloud Azure SQL database. At this moment, the only limitation is that it will not support Azure SQL Managed Instance.

#azure #sql azure #azure sql #azure data sync #azure sql #sql server

Aisu  Joesph

Aisu Joesph


Using Azure Purview to analyze Metadata Insights

In this article, we will learn how to explore the metadata registered in Azure Purview as well as learn how to analyze the metadata insights using the Purview Studio tool.


In any large-scale IT ecosystem composed of tens of data sources and thousands of database objects, managing metadata becomes very vital for an organization to keep the structure of metadata as well as governance on data in check. In my previous articles, we learned about Azure Purview where we understood the overview, features, functionality, aspects, user-interface of the Purview Dashboard, and administration of Purview by different user-persons using Purview Studio, as well as registering data sources and scanning database objects using Purview to extract the metadata information from the data repositories and registering it with Azure Purview service. Once the metadata information starts flowing into Purview, the metadata catalog is created, and it keeps evolving. As the metadata catalog keeps evolving, Purview generates metadata insights that enable a data steward or similar personas to curate the metadata. At the same time using these insights, the end-user persona can also consume the metadata effectively, which is generally the first step before the end-user figures out the metadata objects from which one may want to consume the data. Let’s go ahead and explore metadata registered in purview and also analyze the metadata insights using the Purview Studio tool.


In the previous articles on Azure Purview, we covered how to create a new purview account, navigate the purview studio tool, register new data sources as well as scan these data sources, and extract metadata information that would be registered in purview. It is assumed that this setup is already in place and at least one scan has been performed on one registered data source. In this case, we have scanned an Azure SQL Database instance with the sample data that Azure provides out-of-box. A successful scan of any given data source registered with Azure purview would look as shown below.

Azure Purview Insights

Once the metadata has been created, an easy way to get the first glimpse of the metadata summary is shown in the scan status where it shows the total number of classified assets as well as the total number of discovered assets. We intend to explore more details about the outcomes from the scan. Navigate back to the data source which we would have scanned, and it would look as shown below. It shows an overview of the data source where it details the number of scans performed on the data source, the status of each scan, and summary statistics of the assets that are part of this data source.

There can be multiple assets that may have different assets under them. To find all such data sources that may be registered and cataloged in Azure purview, one can navigate to the Assets section, where it would show all such data sources as shown below.

#azure #sql azure #azure #azure purview

Deion  Hilpert

Deion Hilpert


Application Insights Telemetry Contrast trends using Pin Multiple Entry - Daily .NET Tips

Azure Application Insights is a fully managed Azure Service that helps to monitor the application’s health in real-time. It allows us to track application availability, performance, user session. I have published several tips around application Insights, and here is a really quick and very helpful one. From the individual telemetry entry, you can pin entry to the chart telemetry chart, so that you can contrast trends of multiple entries.

#application insights #azure #application #multiple