Update parallel copy supported scenarios

Author: linda33wj

articles/data-factory/connector-oracle.md

@@ -192,11 +192,10 @@ To copy data from and to Oracle, set the type property of the dataset to `Oracle
 
 This section provides a list of properties supported by the Oracle source and sink. For a full list of sections and properties available for defining activities, see [Pipelines](concepts-pipelines-activities.md). 
 
-### Oracle as a source type
+### Oracle as source
 
-> [!TIP]
->
-> To load data from Oracle efficiently by using data partitioning, see [Parallel copy from Oracle](#parallel-copy-from-oracle).
+>[!TIP]
+>To load data from Oracle efficiently by using data partitioning, see [Parallel copy from Oracle](#parallel-copy-from-oracle).
 
 To copy data from Oracle, set the source type in the copy activity to `OracleSource`. The following properties are supported in the copy activity **source** section.
 
@@ -243,7 +242,7 @@ To copy data from Oracle, set the source type in the copy activity to `OracleSou
 ]
 ```
 
-### Oracle as a sink type
+### Oracle as sink
 
 To copy data to Oracle, set the sink type in the copy activity to `OracleSink`. The following properties are supported in the copy activity **sink** section.
 

articles/data-factory/connector-sap-business-warehouse-open-hub.md

@@ -12,7 +12,7 @@ ms.workload: data-services
 ms.tgt_pltfrm: na
 
 ms.topic: conceptual
-ms.date: 03/08/2019
+ms.date: 08/12/2019
 ms.author: jingwang
 
 ---
@@ -173,6 +173,8 @@ For a full list of sections and properties available for defining activities, se
 
 To copy data from SAP BW Open Hub, set the source type in the copy activity to **SapOpenHubSource**. There are no additional type-specific properties needed in the copy activity **source** section.
 
+To speed up the data loading, you can set [`parallelCopies`](copy-activity-performance.md#parallel-copy) on the copy activity to load data from SAP BW Open Hub in parallel. For example, if you set `parallelCopies` to four, Data Factory concurrently executes four RFC calls, and each RFC call retrieves a portion of data from your SAP BW Open Hub table partitioned by the DTP request ID and package ID. This applies when the number of unique DTP request ID + package ID is bigger than the value of `parallelCopies`.
+
 **Example:**
 
 ```json
@@ -198,7 +200,8 @@ To copy data from SAP BW Open Hub, set the source type in the copy activity to *
             },
             "sink": {
                 "type": "<sink type>"
-            }
+            },
+            "parallelCopies": 4
         }
     }
 ]

articles/data-factory/connector-sap-table.md

@@ -12,7 +12,7 @@ ms.workload: data-services
 ms.tgt_pltfrm: na
 
 ms.topic: conceptual
-ms.date: 08/01/2018
+ms.date: 08/12/2019
 ms.author: jingwang
 
 ---
@@ -198,7 +198,7 @@ To copy data from and to the SAP BW Open Hub linked service, the following prope
 
 For a full list of the sections and properties for defining activities, see [Pipelines](concepts-pipelines-activities.md). The following section provides a list of the properties supported by the SAP table source.
 
-### SAP table as a source
+### SAP table as source
 
 To copy data from an SAP table, the following properties are supported:
 
@@ -220,7 +220,7 @@ To copy data from an SAP table, the following properties are supported:
 <br/>
 >Taking `partitionOption` as `partitionOnInt` as an example, the number of rows in each partition is calculated with this formula: (total rows falling between `partitionUpperBound` and `partitionLowerBound`)/`maxPartitionsNumber`.<br/>
 <br/>
->To run partitions in parallel to speed up copying, we strongly recommend making `maxPartitionsNumber` a multiple of the value of the `parallelCopies` property. For more information, see [Parallel copy](copy-activity-performance.md#parallel-copy).
+>To load data partitions in parallel to speed up copy, the parallel degree is controlled by the [`parallelCopies`](copy-activity-performance.md#parallel-copy) setting on the copy activity. For example, if you set `parallelCopies` to four, Data Factory concurrently generates and runs four queries based on your specified partition option and settings, and each query retrieves a portion of data from your SAP table. We strongly recommend making `maxPartitionsNumber` a multiple of the value of the `parallelCopies` property.
 
 In `rfcTableOptions`, you can use the following common SAP query operators to filter the rows:
 
@@ -266,7 +266,8 @@ In `rfcTableOptions`, you can use the following common SAP query operators to fi
             },
             "sink": {
                 "type": "<sink type>"
-            }
+            },
+            "parallelCopies": 4
         }
     }
 ]

articles/data-factory/connector-teradata.md

@@ -183,11 +183,10 @@ To copy data from Teradata, the following properties are supported:
 
 This section provides a list of properties supported by Teradata source. For a full list of sections and properties available for defining activities, see [Pipelines](concepts-pipelines-activities.md). 
 
-### Teradata as a source type
+### Teradata as source
 
-> [!TIP]
->
-> To load data from Teradata efficiently by using data partitioning, see the [Parallel copy from Teradata](#parallel-copy-from-teradata) section.
+>[!TIP]
+>To load data from Teradata efficiently by using data partitioning, see the [Parallel copy from Teradata](#parallel-copy-from-teradata) section.
 
 To copy data from Teradata, the following properties are supported in the copy activity **source** section:
 

articles/data-factory/copy-activity-performance.md

@@ -160,7 +160,7 @@ To control the load on machines that host your data stores, or to tune copy perf
 **Points to note:**
 
 * When you copy data between file-based stores, **parallelCopies** determines the parallelism at the file level. The chunking within a single file happens underneath automatically and transparently. It's designed to use the best suitable chunk size for a given source data store type to load data in parallel and orthogonal to **parallelCopies**. The actual number of parallel copies the data movement service uses for the copy operation at run time is no more than the number of files you have. If the copy behavior is **mergeFile**, the copy activity can't take advantage of file-level parallelism.
-* When you copy data from stores that aren't file-based (except Oracle database as source with data partitioning enabled) to stores that are file-based, the data movement service ignores the **parallelCopies** property. Even if parallelism is specified, it's not applied in this case.
+* When you copy data from stores that are not file-based (except [Oracle](connector-oracle.md#oracle-as-source), [Teradata](connector-teradata.md#teradata-as-source), [SAP Table](connector-sap-table.md#sap-table-as-source), and [SAP Open Hub](connector-sap-business-warehouse-open-hub#sap-bw-open-hub-as-source) connector as source with data partitioning enabled) to stores that are file-based, the data movement service ignores the **parallelCopies** property. Even if parallelism is specified, it's not applied in this case.
 * The **parallelCopies** property is orthogonal to **dataIntegrationUnits**. The former is counted across all the Data Integration Units.
 * When you specify a value for the **parallelCopies** property, consider the load increase on your source and sink data stores. Also consider the load increase to the self-hosted integration runtime if the copy activity is empowered by it, for example, for hybrid copy. This load increase happens especially when you have multiple activities or concurrent runs of the same activities that run against the same data store. If you notice that either the data store or the self-hosted integration runtime is overwhelmed with the load, decrease the **parallelCopies** value to relieve the load.