You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/synapse-analytics/database-designer/overview-map-data.md
+16-14Lines changed: 16 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,42 +17,44 @@ ms.date: 11/11/2021
17
17
18
18
The Map Data tool is a guided process to help users create ETL mappings and mapping data flows from their source data to Synapse lake database tables without writing code. This process starts with the user choosing the destination tables in Synapse lake databases and then mapping their source data into these tables.
19
19
20
-
For more information on Synapse lake databases see [Overview of Azure Synapse database templates - Azure Synapse Analytics | Microsoft Docs](overview-database-templates.md)
20
+
For more information on Synapse lake databases, see [Overview of Azure Synapse database templates - Azure Synapse Analytics | Microsoft Docs](overview-database-templates.md)
21
21
22
-
Map Data provides for a guided experience where the user can generate a mapping data flow without having to start with a blank canvas and quickly generate a scalable mapping data flow runnable in Synapse pipelines.
23
-
24
-
25
-
> [!NOTE]
26
-
> The Map Data feature in Synapse Analytics pipelines is currently in public preview
22
+
Map Data provides for a guided experience where the user can generate a mapping data flow without having to start with a blank canvas. Then you can quickly generate a scalable mapping data flow runnable in Synapse pipelines.
27
23
28
24
## Getting started
29
25
30
26
The Map Data tool is started from within the Synapse lake database experience. From here, you can select the Map Data tool to begin the process.
31
27
32
-

28
+

33
29
34
30
35
-
Map Data needs compute available to assist users with previewing data and reading schema of their source files. Upon using Map Data for the first time in a session you will need to warm up a cluster.
Map Data needs compute available to assist users with previewing data and reading schema of their source files. Upon using Map Data for the first time in a session, you'll need to warm up a cluster.
To begin, choose your data source that you want to map to your lake database tables. Currently supported data sources are Azure Data Lake Storage Gen 2 and Synapse lake databases.
When choosing a file store such as Azure Data Lake Storage Gen 2 the following file types are supported:
38
+
When choosing a file store, such as Azure Data Lake Storage Gen 2, the following file types are supported:
43
39
44
40
* Common Data Model
45
41
* Delimited Text
46
42
* Parquet
47
43
48
44
49
45
## Create data mapping
46
+
Configure your data mapping with the source type you selected.
47
+

48
+
49
+
> [!NOTE]
50
+
> You can choose a folder or a single file. If you choose a folder you will be able to map multiple files to your lake database tables. If you choose a folder you are also prompted after selecting continue to include only specific files, if desired.
51
+
50
52
Name your data mapping and select the Synapse lake database destination.
51
-

53
+

52
54
53
55
## Source to target mapping
54
56
Choose a Primary source table to map to the Synapse lake database destination table.
55
-

57
+

56
58
57
59
### New mapping
58
60
Use the New Mapping button to add a mapping method to create a mapping or transformation.
@@ -89,4 +91,4 @@ The following mapping methods are supported:
89
91
90
92
## Create pipeline
91
93
92
-
Once you are done with your Map Data transformations select the Create pipeline button to generate a mapping data flow and pipeline to debug and run your transformation.
94
+
Once you're done with your Map Data transformations, select the Create pipeline button to generate a mapping data flow and pipeline to debug and run your transformation.
0 commit comments