Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit d702859

Browse files
authoredJun 3, 2022
Update how-to-sqldb-to-cosmosdb.md
Fixing build suggestions
1 parent bf68c4d commit d702859

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed
 

‎articles/data-factory/how-to-sqldb-to-cosmosdb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ SQL schemas are typically modeled using third normal form, resulting in normaliz
1717

1818
Using Azure Data Factory, we'll build a pipeline that uses a single Mapping Data Flow to read from two Azure SQL Database normalized tables that contain primary and foreign keys as the entity relationship. ADF will join those tables into a single stream using the data flow Spark engine, collect joined rows into arrays and produce individual cleansed documents for insert into a new Azure Cosmos DB container.
1919

20-
This guide will build a new container on the fly called "orders" that will use the ```SalesOrderHeader``` and ```SalesOrderDetail``` tables from the standard SQL Server [Adventure Works sample database](/sql/samples/adventureworks-install-configure?tabs=ssms&view=sql-server-ver15). Those tables represent sales transactions joined by ```SalesOrderID```. Each unique detail records has its own primary key of ```SalesOrderDetailID```. The relationship between header and detail is ```1:M```. We'll join on ```SalesOrderID``` in ADF and then roll each related detail record into an array called "detail".
20+
This guide will build a new container on the fly called "orders" that will use the ```SalesOrderHeader``` and ```SalesOrderDetail``` tables from the standard SQL Server [Adventure Works sample database](/sql/samples/adventureworks-install-configure?tabs=ssms). Those tables represent sales transactions joined by ```SalesOrderID```. Each unique detail records has its own primary key of ```SalesOrderDetailID```. The relationship between header and detail is ```1:M```. We'll join on ```SalesOrderID``` in ADF and then roll each related detail record into an array called "detail".
2121

2222
The representative SQL query for this guide is:
2323

@@ -101,4 +101,4 @@ If everything looks good, you are now ready to create a new pipeline, add this d
101101
## Next steps
102102

103103
* Build the rest of your data flow logic by using mapping data flows [transformations](concepts-data-flow-overview.md).
104-
* [Download the completed pipeline template](https://github.com/kromerm/adfdataflowdocs/blob/master/sampledata/SQL%20Orders%20to%20CosmosDB.zip) for this tutorial and import the template into your factory.
104+
* [Download the completed pipeline template](https://github.com/kromerm/adfdataflowdocs/blob/master/sampledata/SQL%20Orders%20to%20CosmosDB.zip) for this tutorial and import the template into your factory.

0 commit comments

Comments
 (0)
Please sign in to comment.