December 2020 - Page 43 of 95 - Dr. Ware Technology Services

Track the lineage of your organization’s data with Azure Purview

by Contributed | Dec 11, 2020 | Technology

This article is contributed. See the original author and article here.

Trusted data leads to trusted business insights. Ensuring trust in data goes hand-in-hand with making data easily discoverable. One of the ways to do this is by providing data consumers insight into the data’s lineage – where data came from and what transformations it has undergone.

Data lineage in Azure Purview helps organizations to understand the data supply chain, from raw data in hybrid data stores, to business insights in Power BI. Azure Purview’s turnkey integrations with Azure Data Factory, Power BI, Azure Data Share and other Azure Data Services automatically push lineage to Purview Data Map.

Azure Purview also supports Apache Atlas Lineage APIs that can be used to access and update custom lineage in Purview Data Map. Hook & Bridge support from Apache Atlas can also be used to easily push lineage from the Hadoop ecosystem.

Figure 1: Data lineage can be collected from various data systems

Azure Purview can stitch lineage across on-prem, multi-cloud and other platforms

Enterprise data estate contains data systems performing extraction, transformation/load, reporting, ML (machine learning) and so on. The goal of lineage feature in Purview is to capture the data linkage at each data transformation to help answer technical and business questions.

For instance, Purview’s lineage functionality will help capture the data movement and transformation stages such as the one described below.

Data Factory would copy data from on-prem/raw zone to a landing zone in the cloud.

Data processing systems like Synapse, Databricks would process and transform data from landing zone to Curated zone(staging) using notebooks or job definition.

Data Warehouse systems then process the data from staging to dimensional models for optimal query performance and aggregation.

Data Analytics and reporting systems will consume the datasets and process through their meta model to create a BI (Business Intelligence) Dashboard, ML experiments etc

Root cause analysis scenarios

Azure Purview can help data asset owners troubleshoot a dataset or report containing incorrect data because of upstream issues. Data owners can use Azure Purview lineage as a central tool to understand upstream process failures and be informed about the reasons for discrepancies in their data sources.

Figure 2: Azure Purview lineage capability showing troubleshooting steps for a possible issue with Power BI report

Impact analysis scenarios

Data producers can use Azure Purview lineage to evaluate the downstream impact of changes made to their datasets. Lineage can be used as a central platform to know all the consumers of their datasets and understand the impact of any changes to their dependent datasets and reports. For instance, data engineers can evaluate the downstream impact for a deprecating column in a table or change in data type of a column. The data engineers can use Purview lineage to understand the number data assets potentially impacted by the schema changes of an upstream table. The column level lineage precisely points to the specific data assets that are impacted.

Figure 3: Azure Purview lineage capability showing the impact analysis for an upstream change

Lineage sources

Azure Purview can connect with Azure Data Factory, Azure Data Share, Power BI to collect lineage currently. In the coming months many more data systems such as Synapse Analytics, Teradata, SQL Server and so on will be able to connect with Azure Purview for lineage collection.

Call to Action

We are looking forward to hearing, how Azure Purview helped perform troubleshooting and impact analysis of your data pipelines with the native lineage experiences.

Create an Azure Purview account now and start understanding your data supply chain from raw data to business insights with free scanning for all your SQL Server on-premises and Power BI online

Start by connecting a Data Factory or Data Share account to push lineage.

Scan a Power BI tenant to see lineage in Purview. Use managed identity (MSI) authentication to set up a scan of a Power BI tenant

Learn more on lineage user guide.

Azure Sphere OS version 20.12 Update 1 is now available for evaluation

by Contributed | Dec 11, 2020 | Technology

This article is contributed. See the original author and article here.

Azure Sphere OS version 20.12 Update 1 is now available in the Retail Eval feed. This release fixes an Ethernet connection issue for devices with both Wi-Fi and Ethernet enabled. In some cases, upon rebooting the device the Ethernet link-up appeared to be down when it is connected to a network.

This update will not restart the 20.12 evaluation period. The Retail feed will continue to deliver OS version 20.10 until we publish the final 20.12 release next week.

For more information on Azure Sphere OS feeds and setting up an evaluation device group, see Azure Sphere OS feeds.

For self-help technical inquiries, please visit Microsoft Q&A or Stack Overflow. If you require technical support and have a support plan, please submit a support ticket in Microsoft Azure Support or work with your Microsoft Technical Account Manager. If you would like to purchase a support plan, please explore the Azure support plans.

Lesson Learned #155: Timeout period elapsed prior to obtaining a connection from the pool.

by Contributed | Dec 11, 2020 | Technology

This article is contributed. See the original author and article here.

Connection pooling is one of the best practices that we could implement in our code due to improvement in the time spent establishing the connection. However, if we are not aware about it, we may have connectivity issues that may not be related with database service and may be related how our application closes the connection in case of any error, error handling or server client infraestructure level.

In this YouTube session we reviewed three important points when the connection pooling is enabled:

The impact establishing the connection time spent to our Azure SQL database/server.

What is the reason about a typical error when we reached the maximum limit of the connection pooling – Timeout period elapsed prior to obtaining a connection from the pool.

How to obtain connectivity pooling metrics to know how many connections, many connections pool, etc..

Enjoy!

Lesson Learned #155: Timeout period period elapsed prior to obtaining a connection from the pool.

by Contributed | Dec 11, 2020 | Technology

This article is contributed. See the original author and article here.

In this YouTube session we reviewed three important points when the connection pooling is enabled:

The impact establishing the connection time spent to our Azure SQL database/server.

What is the reason about a typical error when we reached the maximum limit of the connection pooling – Timeout period period elapsed prior to obtaining a connection from the pool.