Migrate hierarchical SQL Server data to Azure CosmosDB

Question

I am exploring options to migrate data from SQL Server 2016 into CosmosDB with SQL API. Source data is relational. I need to join them and migrate to CosmosDB db in such a way that each row is migrated as a document. Here is an example.

I want to migrate these individual Product table rows combining it's related ProductSubCatalog table row something like below document.

{              
          "ProductID": 970,                         
          "Name": "Touring-2000 Blue, 46",                         
          "ProductNumber": "BK-T44U-46",                         
          "MakeFlag": true,                         
          "FinishedGoodsFlag": true,                       
          "Color": "Blue",                                                       
          "ModifiedDate": "2014-02-08T10:01:36.827",                   
          "ProductSubCatalog": {                
                       "ProductSubcategoryID": 3,                      
                       "Name": "Touring Bikes"                                                                                 
          }                          
}                          

I tried DocumentDB Data Migration Tool with Source as “SQL” with below query.

SELECT 
    [ProductID],P.[Name], [ProductNumber], [MakeFlag],  
    [FinishedGoodsFlag], [Color], [SafetyStockLevel], [ReorderPoint], 
    [StandardCost], [ListPrice],
    Ps.ProductSubcategoryID AS 'ProductSubCatalog.ProductSubcategoryID', 
    Ps.Name AS 'ProductSubCatalog.Name'   
FROM
    [Production].[Product] P 
LEFT JOIN
    Production.ProductSubcategory PS ON P.ProductSubcategoryID = ps.ProductSubcategoryID
FOR JSON PATH, ROOT('Product')

As the above query generates single JSON data for all rows in Product table, DocumentDB Data Migration Tool imports it as single document. Does someone know other options to achieve this without writing custom application to query to SQL Server data, form JSON document and import it? Any suggestions and pointers will be appreciated.

Answer 1

According to your description, I just followed Import from SQL Server and based on your tables to check this issue.

Note: You do not need to add FOR JSON PATH, ROOT('Product') within your query.

RESULT: