Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into release-2019-cu

Author: v-alje

.openpublishing.redirection.json

@@ -16584,6 +16584,11 @@
       "source_path": "docs/kb-support/index.md",
       "redirect_url": "/sql/sql-server/",
       "redirect_document_id": false
-    }
+    },
+    {
+    "source_path": "docs/database-engine/deprecated-database-engine-features-in-sql-server-version-15.md",
+    "redirect_url": "/sql/database-engine/deprecated-database-engine-features-in-sql-server-2019",
+    "redirect_document_id": true
+  }
   ]
 }

docs/database-engine/deprecated-database-engine-features-in-sql-server-2017.md

@@ -1,5 +1,5 @@
 ---
-title: "Deprecated Database Engine Features | Microsoft Docs"
+title: Deprecated Database Engine Features
 titleSuffix: "SQL Server 2019"
 ms.custom: "seo-lt-2019"
 ms.date: "12/13/2019"

…ine-features-in-sql-server-version-15.md …se-engine-features-in-sql-server-2019.mddocs/database-engine/deprecated-database-engine-features-in-sql-server-version-15.md renamed to docs/database-engine/deprecated-database-engine-features-in-sql-server-2019.md docs/database-engine/deprecated-database-engine-features-in-sql-server-version-15.md renamed to docs/database-engine/deprecated-database-engine-features-in-sql-server-2019.md

@@ -24,7 +24,7 @@ ms.author: chugu
 
   [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] includes features and tools that you can use to troubleshoot packages when you execute them after they have been completed and deployed.  
 
- At design time, [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)] provides breakpoints to pause package execution, the Progress window, and data viewers to watch your data as it passes through the data flow. However, these features are not available when you are running packages that have been deployed. The main techniques for troubleshooting deployed packages are as follows:  
+ At design time, [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)] provides breakpoints to pause package execution, the Progress window, and data viewers. Breakpoints allow you to watch your data as it passes through the data flow. However, these features are not available when you are running deployed packages. The main techniques for troubleshooting deployed packages are as follows:  
 
 -   Catch and handle package errors by using event handlers.  
 
@@ -39,20 +39,20 @@ ms.author: chugu
 -   **Restart packages from the point of failure by using checkpoints**. For more information, see [Restart Packages by Using Checkpoints](../../integration-services/packages/restart-packages-by-using-checkpoints.md).  
 
 ## Catch and Handle Package Errors by Using Event Handlers  
- You can respond to the many events that are raised by the package and the objects in the package by using event handlers.  
+ Use event handlers to respond to events raised by the package and package objects.  
 
--   **Create an event handler for the OnError event**. In the event handler, you can use a Send Mail task to notify an administrator of the failure, use a Script task and custom logic to obtain system information for troubleshooting, or clean up temporary resources or incomplete output. For more information, see [Integration Services (SSIS) Event Handlers](../../integration-services/integration-services-ssis-event-handlers.md).  
+-   **Create an event handler for the OnError event**. In the event handler, you can use a Send Mail task to notify an administrator of the failure. Use a Script task and custom logic to obtain system information for troubleshooting or to clean up temporary resources and incomplete output. For more information, see [Integration Services (SSIS) Event Handlers](../../integration-services/integration-services-ssis-event-handlers.md).  
 
 ## Troubleshoot Bad Data by Using Error Outputs  
  You can use the error output available on many data flow components to direct rows that contain errors to a separate destination for later analysis. For more information, see [Error Handling in Data](../../integration-services/data-flow/error-handling-in-data.md).  
 
 -   **Capture bad data by using error outputs**. Send rows that contain errors to a separate destination such as an error table or a text file. The error output automatically adds two numeric columns that contain the number of the error that caused the row to be rejected, and the ID of the column in which the error occurred.  
 
--   **Add friendly information to the error outputs**. You can make it easier to analyze the error output by adding the error message and the column name in addition to the two numeric identifiers that are supplied by the error output. For an example of how to add these two additional columns by using scripting, see [Enhancing an Error Output with the Script Component](../../integration-services/extending-packages-scripting-data-flow-script-component-examples/enhancing-an-error-output-with-the-script-component.md).  
+-   **Add friendly information to the error outputs**. To improve the clarity of error output, add the error message and the column name in addition to the two numeric identifiers that are supplied by the error output. For an example of how to add these two additional columns by using scripting, see [Enhancing an Error Output with the Script Component](../../integration-services/extending-packages-scripting-data-flow-script-component-examples/enhancing-an-error-output-with-the-script-component.md).  
 
 -   **Or, get the column names by logging the DiagnosticEx event**. This event writes a data flow lineage map to the log. You can then look up the column name in this lineage map by using the column identifier captured by an error output.  For more info, see [Error Handling in Data](../../integration-services/data-flow/error-handling-in-data.md).  
 
-     The value of the message column for **DiagnosticEx** is XML text. To view the message text for a package execution, query the [catalog.operation_messages (SSISDB Database)](../../integration-services/system-views/catalog-operation-messages-ssisdb-database.md) view. Note that the **DiagnosticEx** event does not preserve whitespace in its XML output to reduce the size of the log. To improve readability, copy the log into an XML editor - in Visual Studio, for example - that supports XML formatting and syntax highlighting.  
+     The value of the message column for **DiagnosticEx** is XML text. To view the message text for a package execution, query the [catalog.operation_messages (SSISDB Database)](../../integration-services/system-views/catalog-operation-messages-ssisdb-database.md) view. Note the **DiagnosticEx** event does not preserve whitespace in its XML output to reduce the size of the log. To improve readability, copy the log into an XML editor - in Visual Studio, for example - that supports XML formatting and syntax highlighting.  
 
 ## Troubleshoot Package Execution by Using Operations Reports  
  Standard operations reports are available in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to help you monitor [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages that have been deployed to the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] catalog. These package reports help you to view package status and history, and, if necessary, identify the cause of failures.  
@@ -63,7 +63,7 @@ ms.author: chugu
  A number of SSISDB database views are available that you can query to monitor package execution and other operations information. For more information, see [Monitor Running Packages and Other Operations](../../integration-services/performance/monitor-running-packages-and-other-operations.md).  
 
 ## Troubleshoot Package Execution by Using Logging  
- You can track much of what occurs in your running packages by enabling logging. Log providers capture information about the specified events for later analysis, and save that information in a database table, a flat file, an XML file, or another supported output format.  
+ You can track much of what occurs in your running packages with logging. Log providers capture information about the specified events for later analysis, and save that information in one of several supported formats.  Support log provider formats include database table, a flat file, an XML file.  
 
 -   **Enable logging**. You can refine the logging output by selecting only the events and only the items of information that you want to capture. For more information, see [Integration Services (SSIS) Logging](../performance/integration-services-ssis-logging.md).  
 
@@ -77,7 +77,7 @@ ms.author: chugu
 
     2.  **Add auditing information to the data flow**. You can use the Audit transformation to add information to rows in the data flow about the package execution that created or modified each row. The Audit transformation makes nine pieces of information available, including the PackageName and ExecutionInstanceGUID. For more information, see [Audit Transformation](../../integration-services/data-flow/transformations/audit-transformation.md). If you have custom information that you would also like to include in each row for auditing purposes, you can add this information to rows in the data flow by using a Derived Column transformation. For more information, see [Derived Column Transformation](../../integration-services/data-flow/transformations/derived-column-transformation.md).  
 
-    3.  **Consider capturing row count data**. Consider creating a separate table for row count information, where each instance of package execution is identified by its ExecutionID. Use the Row Count transformation to save the row count into a series of variables at critical points in the data flow. After the data flow ends, use an Execute SQL task to insert the series of values into a row in the table for later analysis and reporting.  
+    3.  **Consider capturing row count data**. Consider creating a separate table for row count information, where each instance of package execution is identified by its ExecutionID. Use the Row Count transformation to save the row count into a series of variables at critical points in the data flow. Add an Execute SQL task to insert the series of values into a row in the table for later analysis and reporting.  
 
      For more information about this approach, see the section, "ETL Auditing and Logging," in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] white paper, [Project REAL: Business Intelligence ETL Design Practices](https://www.microsoft.com/download/details.aspx?id=14582).  
 
@@ -87,7 +87,7 @@ ms.author: chugu
 ## Troubleshoot Run-time Validation Issues  
  Sometimes you might not be able to connect to your data sources, or portions of your package cannot be validated, until prior tasks in the package have executed. [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] includes the following features to help you avoid the validation errors that would otherwise result from these conditions:  
 
--   **Configure the DelayValidation property on package elements that are not valid when the package is loaded**. You can set **DelayValidation** to **True** on package elements whose configuration is not valid, to prevent validation errors when the package is loaded. For example, you may have a Data Flow task that uses a destination table that does not exist until an Execute SQL task creates the table at run time. The **DelayValidation** property can be enabled at the package level, or at the level of the individual tasks and containers that the package includes.  
+-   **Configure the DelayValidation property on known invalid package elements**. To prevent validation errors for package elements with known configuration problems, set **DelayValidation** to **True**. For example, the package contains a Data Flow task that uses a destination table that does not exist until an Execute SQL task creates the table at run time. The **DelayValidation** property can be enabled at the package level, or at the level of the individual tasks and containers that the package includes.  
 
      The **DelayValidation** property can be set on a Data Flow task, but not on individual data flow components. You can achieve a similar effect by setting the <xref:Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100.ValidateExternalMetadata%2A> property of individual data flow components to **false**. However, when the value of this property is **false**, the component is not aware of changes to the metadata of external data sources. When set to **true**, the <xref:Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100.ValidateExternalMetadata%2A> property can help to avoid blocking issues caused by locking in the database, especially when the package is using transactions.  
 
@@ -101,10 +101,7 @@ ms.author: chugu
 -   **Some data providers are not available on the 64-bit platform**. In particular, the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Jet OLE DB Provider that is required to connect to Excel or Access data sources is not available in a 64-bit version.  
 
 ## Troubleshoot Errors without a Description  
- If you encounter an [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] error that does not have an accompanying description, you can locate the description in [Integration Services Error and Message Reference](../../integration-services/integration-services-error-and-message-reference.md) by looking up the error by its number. The list does not include troubleshooting information at this time.  
+ If you encounter an [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] error that does not have an accompanying description, you can locate the description in [Integration Services Error and Message Reference](../../integration-services/integration-services-error-and-message-reference.md). The list does not currently include troubleshooting information.  
 
 ## Related Tasks  
- [Debugging Data Flow](../../integration-services/troubleshooting/debugging-data-flow.md)  
-  
-## Related Content  
- Blog entry, [Adding the error column name to an error output](https://go.microsoft.com/fwlink/?LinkId=261546), on dougbert.com.  
+ [Debugging Data Flow](../../integration-services/troubleshooting/debugging-data-flow.md)

docs/integration-services/troubleshooting/troubleshooting-tools-for-package-execution.md

@@ -223,6 +223,7 @@ The following features and services are not available SQL Server 2017 on Linux.
 |   | Alerts |
 |   | Log Reader Agent |
 |   | Managed Backup |
+|   | Multi-Server Administration using MSX/TSX |
 | **High Availability** | Database mirroring  |
 | **Security** | Extensible Key Management |
 |   | AD Authentication for Linked Servers | 

docs/linux/sql-server-linux-editions-and-components-2017.md

@@ -221,6 +221,7 @@ The following features and services are not available for SQL Server 2019 on Lin
 | **SQL Server Agent** |  Subsystems: CmdExec, PowerShell, Queue Reader, SSIS, SSAS, SSRS |
 |   | Alerts |
 |   | Managed Backup |
+|   | Multi-Server Administration using MSX/TSX |
 | **High Availability** | Database mirroring  |
 | **Security** | Extensible Key Management |
 |   | AD Authentication for Linked Servers | 

docs/linux/sql-server-linux-editions-and-components-2019.md

@@ -17,7 +17,7 @@ ms.author: genemi
 ---
 # ODBC Driver for Oracle
 > [!IMPORTANT]  
->  This feature will be removed in a future version of Windows. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Instead, use the ODBC driver provided by Oracle.  
+>  This feature will be removed in a future version of Windows. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Instead, use the [ODBC driver provided by Oracle](https://www.oracle.com/database/technologies/releasenote-odbc-ic.html).  
   
  The Microsoft® ODBC Driver for Oracle allows you to connect your ODBC-compliant application to an Oracle database. The ODBC Driver for Oracle conforms to the Open Database Connectivity (ODBC) specification described in the *ODBC Programmer's Reference*. It allows access to PL/SQL packages, XA/DTC integration, and Oracle access from within Internet Information Services (IIS).  
 

docs/odbc/microsoft/odbc-driver-for-oracle.md

@@ -1,7 +1,7 @@
 ---
 title: "xp_cmdshell (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/01/2019"
+ms.date: "03/30/2020"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.reviewer: ""
@@ -64,7 +64,7 @@ The command(s) completed successfully.
  **xp_cmdshell** can be enabled and disabled by using the Policy-Based Management or by executing **sp_configure**. For more information, see [Surface Area Configuration](../../relational-databases/security/surface-area-configuration.md) and [xp_cmdshell Server Configuration Option](../../database-engine/configure-windows/xp-cmdshell-server-configuration-option.md).  
 
 > [!IMPORTANT]
->  If **xp_cmdshell** is executed within a batch and returns an error, the batch will fail. This is a change of behavior. In earlier versions of [!INCLUDE[msCoName](../../includes/msconame-md.md)][!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] the batch would continue to execute.  
+>  If **xp_cmdshell** is executed within a batch and returns an error, the batch will fail.
   
 ## xp_cmdshell Proxy Account  
  When it is called by a user that is not a member of the **sysadmin** fixed server role, **xp_cmdshell** connects to Windows by using the account name and password stored in the credential named **##xp_cmdshell_proxy_account##**. If this proxy credential does not exist, **xp_cmdshell** will fail.  

docs/relational-databases/system-stored-procedures/xp-cmdshell-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "Querying Data in a System-Versioned Temporal Table | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/28/2016"
+ms.date: "03/30/2020"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.reviewer: ""
@@ -26,7 +26,7 @@ To perform any type of time-based analysis, use the new **FOR SYSTEM_TIME** clau
 - CONTAINED IN (<start_date_time> , <end_date_time>)
 - ALL
 
-**FOR SYSTEM_TIME** can be specified independently for each table in a query. It can be used inside common table expressions, table-valued functions and stored procedures. When using a table alias with a temporal tables, the **FOR SYSTEM_TIME** clause must included between the temporal table name and the alias (see "Query for a specific time using the AS OF sub-clause" second example, below).
+**FOR SYSTEM_TIME** can be specified independently for each table in a query. It can be used inside common table expressions, table-valued functions and stored procedures. When using a table alias with a temporal tables, the **FOR SYSTEM_TIME** clause must included between the temporal table name and the alias - see the second example in [Query for a specific time using the AS OF sub-clause](#query-for-a-specific-time-using-the-as-of-sub-clause).
 
 ## Query for a specific time using the AS OF sub-clause