more updates

Author: codingbandit

Extensions/AzureTableAPI/README.md

@@ -2,6 +2,8 @@
 
 This extension is built to facilitate both a data Source and Sink for the migration tool to be able to read and write to Azure Table API. This covers both the Azure Storage Table API and Azure Cosmos DB Table API, since they both adhere to the same API spec.
 
+> **Note**: When specifying the AzureTableAPI extension as the Source or Sink property in configuration, utilize the name **AzureTableAPI**.
+> 
 ## Configuration Settings
 
 The AzureTableAPI has a couple required and optional settings for configuring the connection to the Table API you are connecting to. This applies to both Azure Storage Table API and Azure Cosmos DB Table API.

Extensions/Cosmos/README.md

@@ -2,6 +2,8 @@
 
 The Cosmos data transfer extension provides source and sink capabilities for reading from and writing to containers in Cosmos DB using the Core (SQL) API. Source and sink both support string, number, and boolean property values, arrays, and hierarchical nested object structures.
 
+> **Note**: When specifying the JSON extension as the Source or Sink property in configuration, utilize the name **Cosmos-nosql**.
+
 ## Settings
 
 Source and sink settings both require multiple parameters to specify and provide access to the data location within a Cosmos DB account: 

Extensions/Json/README.md

@@ -2,6 +2,8 @@
 
 The JSON data transfer extension provides source and sink capabilities for reading from and writing to JSON files. Source and sink both support string, number, and boolean property values, arrays, and hierarchical nested object structures.
 
+> **Note**: When specifying the JSON extension as the Source or Sink property in configuration, utilize the name **JSON**.
+
 ## Settings
 
 Source and sink settings both require a `FilePath` parameter, which should specify a path to a JSON file or folder containing JSON files. The path can be either absolute or relative to the application. The JSON files can contain either an array of JSON objects or a single object. Sink also supports an optional `Indented` parameter (`false` by default) and an optional `IncludeNullFields` parameter (`false` by default) to control the formatting of the JSON output.

Extensions/Mongo/README.md

@@ -2,6 +2,8 @@
 
 The Mongo data transfer extension provides source and sink capabilities for reading from and writing to a Mongo database.
 
+> **Note**: When specifying the Mongo extension as the Source or Sink property in configuration, utilize the name **Mongo**.
+> 
 ## Settings
 
 Source and sink settings require both `ConnectionString` and `DatabaseName` parameters. The source takes an optional `Collection` parameter (if this parameter is not set, it will read from all collections). The sink requires the `Collection` parameter and will insert all records received from a source into that collection, as well as an optional `BatchSize` parameter (default value is 100) to batch the writes into the collection.

Extensions/SqlServer/README.md

@@ -2,6 +2,8 @@
 
 The SQL Server data transfer extension provides source and sink capabilities for reading from and writing to table data in SQL Server. Hierarchical data is not fully supported but the Sink extension will write a nested object from a hierarchical source (i.e. JSON, Cosmos) into a SQL column as a JSON string.
 
+> **Note**: When specifying the SQL Server extension as the Source or Sink property in configuration, utilize the name **SqlServer**.
+
 ## Settings
 
 Source and sink settings both require a `ConnectionString` parameter.

README.md

@@ -108,7 +108,9 @@ This tutorial outlines how to use the Cosmos DB Data Migration tool to move JSON
 
     ```json
     {
-        "SourceSettings": {            
+        "Source": "JSON",
+        "Sink": "Cosmos-nosql",
+        "SourceSettings": {
             "FilePath": "C:\\btcdata\\simple_json.json"
         },
         "SinkSettings": {
@@ -126,41 +128,9 @@ This tutorial outlines how to use the Cosmos DB Data Migration tool to move JSON
 
 3. Ensure the **Cosmos.DataTransfer.Core** project is set as the startup project then press <kbd>F5</kbd> to run the application.
 
-4. The application will load the provided extensions, then prompt for a **Source**. Select **JSON**. When prompted to load settings from a file enter `n` and press <kbd>Enter</kbd>. The application provides the ability to configure extensions in a separate file versus having them located in the **migrationsettings.json** file. When a separate file is not specified, the settings are read from **migrationsettings.json**. When prompted to provide the Configuration section name, press <kbd>Enter</kbd> to accept the default: **JSONSourceSettings**.
-
-    ![The Data Migration application displays with a menu prompt for Source.](media/app_source_prompt.png "Select Source")
-
-    >**Note**: Alternatively, to avoid this prompt add the **Source** property to the configuration with the value **Json** (matching the **DisplayName** property of the extension)
-
-5. The application will then prompt for a **Sink**, choose **Cosmos-nosql**. When prompted to load settings from a file enter `n` and press <kbd>Enter</kbd>. The application provides the ability to configure extensions in a separate file versus having them located in the **migrationsettings.json** file. When a separate file is not specified, the settings are read from **migrationsettings.json**. When prompted to provide the Configuration section name, press <kbd>Enter</kbd> to accept the default: **Cosmos-NoSqlSinkSettings**.
+4. The application then performs the data migration. After a few moments the process will indicate **Done.**.
 
-    ![The Data migration application displays with a menu prompt for Sink.](media/app_sink_prompt.png "Select Sink")
-
-    >**Note**: Alternatively, to avoid this prompt add the **Sink** property to the configuration with the value **Cosmos-nosql** (matching the **DisplayName** property of the extension)
-
-6. The application then performs the data migration. After a few moments the process will indicate **Done.**.
-
-    ![The Data migration application displays with the full output of the migration including the Done message.](media/app_final.png "Data Migration completes")
-
-Example of `migrationsettings.json` with **Source** and **Sink** configured.
-
-```json
-{
-  "Source": "JSON",
-  "Sink": "Cosmos-nosql",
-  "SourceSettings": {
-    "FilePath": "C:\\btcdata\\simple_json.json"
-  },
-  "SinkSettings": {
-    "ConnectionString": "AccountEndpoint=https://localhost:8081/;AccountKey=C2y6yDj...",
-    "Database": "datamigration",
-    "Container": "btcdata",
-    "PartitionKeyPath": "/id",
-    "RecreateContainer": false,
-    "IncludeMetadataFields": false
-  }
-}
-```
+>**Note**: The `Source` and `Sink` properties should match the **DisplayName** set in the code for the extensions.
 
 ## Using the command line