Skip to content

Commit d7d7713

Browse files
committed
Register -- update author, date, acrolinx.
1 parent fe43c0c commit d7d7713

File tree

1 file changed

+18
-11
lines changed

1 file changed

+18
-11
lines changed
Lines changed: 18 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,26 @@
11
---
22
title: Register data sources in Azure Data Catalog
33
description: This article highlights how to register data sources in Azure Data Catalog, including the metadata fields extracted during registration.
4-
author: JasonWHowell
5-
ms.author: jasonh
4+
author: ChandraKavya
5+
ms.author: kchandra
66
ms.service: data-catalog
77
ms.topic: how-to
8-
ms.date: 08/01/2019
8+
ms.date: 02/25/2022
99
---
10+
1011
# Register data sources in Azure Data Catalog
1112

1213
[!INCLUDE [Azure Purview redirect](../../includes/data-catalog-use-purview.md)]
1314

1415
## Introduction
16+
1517
Azure Data Catalog is a fully managed cloud service that serves as a system of registration and discovery for enterprise data sources. In other words, Data Catalog helps people discover, understand, and use data sources, and it helps organizations get more value from their existing data. The first step to making a data source discoverable via Data Catalog is to register that data source.
1618

1719
## Register data sources
20+
1821
Registration is the process of extracting metadata from the data source and copying that data to the Data Catalog service. The data remains where it currently resides, and it remains under the control of the administrators and policies of the current system.
1922

20-
To register a data source, do the following:
23+
To register a data source, follow these steps:
2124
1. In the Azure Data Catalog portal, start the Data Catalog data source registration tool.
2225
2. Sign in with your work or school account with the same Azure Active Directory credentials that you use to sign in to the portal.
2326
3. Select the data source you want to register.
@@ -27,29 +30,32 @@ For more step-by-step details, see the [Get Started with Azure Data Catalog](dat
2730
After you've registered the data source, the catalog tracks its location and indexes its metadata. Users can search, browse, and discover the data source, and then use its location to connect to it by using the application or tool of their choice.
2831

2932
## Supported data sources
33+
3034
For a list of currently supported data sources, see [Data Catalog DSR](data-catalog-dsr.md).
3135

3236
## Structural metadata
37+
3338
When you register a data source, the registration tool extracts information about the structure of the objects you select. This information is referred to as structural metadata.
3439

3540
For all objects, this structural metadata includes the object’s location, so that users who discover the data can use that information to connect to the object in the client tools of their choice. Other structural metadata includes object name and type, and attribute/column name and data type.
3641

3742
## Descriptive metadata
43+
3844
In addition to the core structural metadata that's extracted from the data source, the data source registration tool extracts descriptive metadata. For SQL Server Analysis Services and SQL Server Reporting Services, this metadata is taken from the Description properties exposed by these services. For SQL Server, values provided using the ms\_description extended property is extracted. For Oracle Database, the data-source registration tool extracts the COMMENTS column from the ALL\_TAB\_COMMENTS view.
3945

4046
In addition to the descriptive metadata that's extracted from the data source, users can enter descriptive metadata by using the data source registration tool. Users can add tags, and they can identify experts for the objects being registered. All this descriptive metadata is copied to the Data Catalog service along with the structural metadata.
4147

4248
## Include previews
49+
4350
By default, only metadata is extracted from data sources and copied to the Data Catalog service, but understanding a data source is often made easier when you can view a sample of the data it contains.
4451

45-
By using the Data Catalog data-source registration tool, you can include a snapshot preview of the data in each table and view that is registered. If you choose to include previews during registration, the registration tool includes up to 20 records from each table and view. This snapshot is then copied to the catalog along with the structural and descriptive metadata.
52+
You can include a snapshot preview of the data in each table and view that is registered, using the Data Catalog data-source registration tool. If you choose to include previews during registration, the registration tool includes up to 20 records from each table and view. This snapshot is then copied to the catalog along with the structural and descriptive metadata.
4653

4754
> [!NOTE]
4855
> Wide tables with a large number of columns might have fewer than 20 records included in their preview.
49-
>
50-
>
5156
5257
## Include data profiles
58+
5359
Just as including previews can provide valuable context for users who search for data sources in Data Catalog, including a data profile can make it easier to understand discovered data sources.
5460

5561
By using the Data Catalog data-source registration tool, you can include a data profile for each table and view that is registered. If you choose to include a data profile during registration, the registration tool includes aggregate statistics about the data in each table and view, including:
@@ -63,16 +69,17 @@ These statistics are then copied to the catalog along with the structural and de
6369

6470
> [!NOTE]
6571
> Text and date columns do not include average or standard deviation statistics in their data profile.
66-
>
67-
>
6872
6973
## Update registrations
70-
Registering a data source makes it discoverable in Data Catalog when you use the metadata and optional preview extracted during registration. If the data source needs to be updated in the catalog (for example, if the schema of an object has changed, tables originally excluded should be included, or you want to update the data that's included in the previews), the data source registration tool can be re-run.
74+
75+
Registering a data source makes it discoverable in Data Catalog when you use the metadata and optional preview extracted during registration. If the data source needs to be updated in the catalog (for example, if the schema of an object has changed, tables originally excluded should be included, or you want to update the data that's included in the previews), the data source registration tool can be rerun.
7176

7277
Re-registering an already-registered data source performs a merge “upsert” operation: existing objects are updated, and new objects are created. Any metadata provided by users through the Data Catalog portal are retained.
7378

7479
## Summary
75-
Because it copies structural and descriptive metadata from a data source to the catalog service, registering the data source in Data Catalog makes the data easier to discover and understand. After you have registered the data source, you can annotate, manage, and discover it by using the Data Catalog portal.
80+
81+
Because it copies structural and descriptive metadata from a data source to the catalog service, registering the data source in Data Catalog makes the data easier to discover and understand. After you've registered the data source, you can annotate, manage, and discover it by using the Data Catalog portal.
7682

7783
## Next steps
84+
7885
For more information about registering data sources, see the [Get Started with Azure Data Catalog](data-catalog-get-started.md) tutorial.

0 commit comments

Comments
 (0)