Update Copy into Azure Synapse Analytics DIU

Author: Clare Zheng (Shanghai Wicresoft Co Ltd)

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

@@ -33,7 +33,7 @@ The allowed DIUs to empower a copy activity run is **between 4 and 256**. If not
 | Copy scenario | Supported DIU range | Default DIUs determined by service |
 |:--- |:--- |---- |
 | Between file stores |- **Copy from or to single file**: 4 <br>- **Copy from and to multiple files**: 4-256 depending on the number and size of the files <br><br>For example, if you copy data from a folder with 4 large files and choose to preserve hierarchy, the max effective DIU is 16; when you choose to merge file, the max effective DIU is 4. |Between 4 and 32 depending on the number and size of the files |
-| From file store to non-file store |- **Copy from single file**: 4 <br/>- **Copy from multiple files**: 4-256 depending on the number and size of the files <br/><br/>For example, if you copy data from a folder with 4 large files, the max effective DIU is 16. |- **Copy into Azure SQL Database or Azure Cosmos DB**: between 4 and 16 depending on the sink tier (DTUs/RUs) and source file pattern<br>- **Copy into Azure Synapse Analytics** using PolyBase or COPY statement: 4<br>- Other scenario: 4 |
+| From file store to non-file store |- **Copy from single file**: 4 <br/>- **Copy from multiple files**: 4-256 depending on the number and size of the files <br/><br/>For example, if you copy data from a folder with 4 large files, the max effective DIU is 16. |- **Copy into Azure SQL Database or Azure Cosmos DB**: between 4 and 16 depending on the sink tier (DTUs/RUs) and source file pattern<br>- **Copy into Azure Synapse Analytics** using PolyBase or COPY statement: 2<br>- Other scenario: 4 |
 | From non-file store to file store |- **Copy from partition-option-enabled data stores** (including [Azure Database for PostgreSQL](connector-azure-database-for-postgresql.md#azure-database-for-postgresql-as-source), [Azure SQL Database](connector-azure-sql-database.md#azure-sql-database-as-the-source), [Azure SQL Managed Instance](connector-azure-sql-managed-instance.md#sql-managed-instance-as-a-source), [Azure Synapse Analytics](connector-azure-sql-data-warehouse.md#azure-synapse-analytics-as-the-source), [Oracle](connector-oracle.md#oracle-as-source), [Netezza](connector-netezza.md#netezza-as-source), [SQL Server](connector-sql-server.md#sql-server-as-a-source), and [Teradata](connector-teradata.md#teradata-as-source)): 4-256 when writing to a folder, and 4 when writing to one single file. Note per source data partition can use up to 4 DIUs.<br>- **Other scenarios**: 4 |- **Copy from REST or HTTP**: 1<br/>- **Copy from Amazon Redshift** using UNLOAD: 4<br>- **Other scenario**: 4 |
 | Between non-file stores |- **Copy from partition-option-enabled data stores** (including [Azure Database for PostgreSQL](connector-azure-database-for-postgresql.md#azure-database-for-postgresql-as-source), [Azure SQL Database](connector-azure-sql-database.md#azure-sql-database-as-the-source), [Azure SQL Managed Instance](connector-azure-sql-managed-instance.md#sql-managed-instance-as-a-source), [Azure Synapse Analytics](connector-azure-sql-data-warehouse.md#azure-synapse-analytics-as-the-source), [Oracle](connector-oracle.md#oracle-as-source), [Netezza](connector-netezza.md#netezza-as-source), [SQL Server](connector-sql-server.md#sql-server-as-a-source), and [Teradata](connector-teradata.md#teradata-as-source)): 4-256 when writing to a folder, and 4 when writing to one single file. Note per source data partition can use up to 4 DIUs.<br/>- **Other scenarios**: 4 |- **Copy from REST or HTTP**: 1<br>- **Other scenario**: 4 |