Merge pull request #18067 from MicrosoftDocs/master

12/09 AM Publish

Author: huypub

docs/database-engine/install-windows/upgrade-analysis-services.md

@@ -2,7 +2,7 @@
 description: "Upgrade Analysis Services"
 title: "Upgrade Analysis Services | Microsoft Docs"
 ms.custom: ""
-ms.date: "09/12/2017"
+ms.date: "12/09/2020"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: 
@@ -75,6 +75,7 @@ manager: erikre
 
 |Database model|Compatibility level|Compatible versions|  
 |-|-|-|  
+|Tabular|1500|SQL Server 2019|
 |Tabular|1400|SQL Server 2017|
 |Tabular|1200|SQL Server 2016|  
 |Tabular|1103|SQL Server 2014|  

docs/relational-databases/import-export/prepare-data-for-bulk-export-or-import-sql-server.md

@@ -57,7 +57,7 @@ ms.custom: "seo-lt-2019"
   
 -   To import data from data files with fixed-length or fixed-width fields, use a format file. For more information, see [XML Format Files (SQL Server)](../../relational-databases/import-export/xml-format-files-sql-server.md).  
 
--   Comma-separated value (CSV) files are not supported by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] bulk-import operations. However, in some cases, a CSV file can be used as the data file for a bulk import of data into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Note that the field terminator of a CSV file does not have to be a comma. To be usable as a data file for bulk import, a CSV file must comply with the following restrictions:  
+-  Starting with SQL Server 2017, a CSV file can be used as the data file for a bulk import of data into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Note that the field terminator of a CSV file does not have to be a comma. To be usable as a data file for bulk import, a CSV file must comply with the following restrictions:  
 
     -   Data fields never contain the field terminator.  
 

docs/relational-databases/replication/agents/replication-merge-agent.md

@@ -286,7 +286,12 @@ replmerg [-?]
  Specifies whether the output should be verbose. If the verbose level is **0**, only error messages are printed. If the verbose level is **1**, all of the progress report messages are printed. If the verbose level is **2** (default), all error messages and progress report messages are printed, which is useful for debugging.  
 
  **-ParallelUploadDownload** [**0**\|**1**]  
- Specifies whether the Merge Agent should process in parallel the changes uploaded to the Publisher and those downloaded to the Subscriber, which is useful in high volume environments with high network bandwidth. If **ParallelUploadDownload** is **1**, then parallel processing is enabled.  
+ Specifies whether the Merge Agent should process in parallel the changes uploaded to the Publisher and those downloaded to the Subscriber, which can be useful in high volume environments with high network bandwidth. However, note the warning below for cases where **ParallelUploadDownload** is set to **1**.
+ 
+This parameter is on the list for possible deprecation soon. We recommend setting the **ParallelUploadDownload** parameter to 0 and avoiding use of the "High Volume Server-to-Server" Merge agent Profile, as **ParallelUploadDownload** is set to 1 in this profile.
+
+> [!WARNING]
+>  [!INCLUDE[ssNoteDepFutureDontUse](../../../includes/ssnotedepfuturedontuse-md.md)]
   
  **-PacketSize**  
  Is the packet size, in bytes. The default is 4096 (bytes).  

docs/relational-databases/replication/non-sql/heterogeneous-database-replication.md

@@ -28,7 +28,7 @@ ms.author: "mathoma"
   |Scenario|2016 or earlier |2017 or later |
   |-------|-------|--------|
   |Replication from Oracle |Only support Oracle 10g or earlier |Only support Oracle 10g or earlier |
-  |Replication to Oracle |Up to Oracle 12c |Not supported |
+  |Replication to Oracle |All versions prior to Oracle 12c |Not supported |
 
 
  Heterogeneous replication to non-SQL Server subscribers is deprecated. Oracle Publishing is deprecated. To move data, create solutions using change data capture and [!INCLUDE[ssIS](../../../includes/ssis-md.md)].  

docs/sql-server/failover-clusters/install/before-installing-failover-clustering.md

@@ -164,7 +164,7 @@ ms.author: chadam
 
 -   Remote Administration must be enabled.  
 
--   For the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] port, use [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager to check the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] network configuration for the TCP/IP protocol for the instance you want to unblock. You must enable the TCP port for IPALL if you want to connect to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] using TCP after installation. By default, SQL Browser listens on UDP port 1434.  
+- For SQL Server instances using a non-default port, use the network configuration of the SQL Server Configuration Manager to determine the port used by the SQL Server instance you want to unblock. Enable the TCP port for IPALL in the firewall if you want to connect to your SQL Server instance using the [SQL Server Browser Service](../../../tools/configuration-manager/sql-server-browser-service.md), which uses a different IP address than the clustered instance, and UDP port 1434. 
 
 -   Failover cluster Setup operations include a rule that checks network binding order. Although binding orders might seem correct, you might have disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC configurations can affect the binding order and cause the binding order rule to issue a warning. To avoid this situation, use the following steps to identify and remove disabled network adapters: