Merge pull request #3694 from MicrosoftDocs/master

10/27 AM Publish

Author: v-alje

docs/analysis-services/what-s-new-in-sql-server-analysis-services-2017.md

@@ -1,6 +1,6 @@
 ---
 title: "What's new in SQL Server 2017 Analysis Services | Microsoft Docs"
-ms.date: "10/03/2017"
+ms.date: "10/27/2017"
 ms.prod: "sql-server-2017"
 ms.reviewer: ""
 ms.suite: ""
@@ -41,9 +41,9 @@ To upgrade an existing tabular model in SSDT, in Solution Explorer, right-click
 It's important to keep in mind, once you upgrade an existing model to 1400, you can't downgrade. Be sure to keep a backup of your 1200 model database.
 
 ## Modern Get Data experience
-When it comes to ingesting data from data sources into your tabular models, SQL Server Data Tools (SSDT) introduces the modern **Get Data** experience for models at the 1400 compatibility level. This new feature is based on similar functionality in Power BI Desktop and Microsoft Excel 2016. The modern Get Data experience provides immense data transformation and data mashup capabilities by using the Get Data query builder and M expressions.
+When it comes to importing data from data sources into your tabular models, SQL Server Data Tools (SSDT) introduces the modern **Get Data** experience for models at the 1400 compatibility level. This new feature is based on similar functionality in Power BI Desktop and Microsoft Excel 2016. The modern Get Data experience provides immense data transformation and data mashup capabilities by using the Get Data query builder and M expressions.
 
-The modern Get Data experience provided support for a wide range of additional data source. Future updates will support additional data sources.
+The modern Get Data experience provides support for a wide range of data sources. Going forward, updates will include support for even more.
 
 ![AS_Get_Data_in_SSDT](../analysis-services/media/as-get-data-in-ssdt.png)
 

docs/integration-services/change-data-capture/process-inserts-updates-and-deletes.md

@@ -32,7 +32,7 @@ ms.workload: "Inactive"
   
  Matching an ordinal value to its corresponding operation is not as easy as using a mnemonic of the operation. For example, 'D' can easily represent a delete operation and 'I' represent an insert operation. The example query that was created in the topic, [Creating the Function to Retrieve the Change Data](../../integration-services/change-data-capture/create-the-function-to-retrieve-the-change-data.md), makes this conversion from an ordinal value to a friendly string value that is returned in a new column. The following segment of code shows this conversion:  
 
-```  
+```sql
 select   
     ...  
     case __$operation  

docs/integration-services/change-data-capture/specify-an-interval-of-change-data.md

@@ -90,7 +90,7 @@ ms.workload: "Inactive"
 
     4.  For **SQLStatement**, enter the following SQL statement:  
 
-        ```  
+        ```sql
         SELECT DATEADD(dd,0, DATEDIFF(dd,0,GETDATE()-1)) AS ExtractStartTime,  
           DATEADD(dd,0, DATEDIFF(dd,0,GETDATE())) AS ExtractEndTime  
 

docs/integration-services/data-flow/data-streaming-destination.md

@@ -24,7 +24,7 @@ ms.workload: "Inactive"
 
  In the following example example, the following query returns output from the Package.dtsx package in the SSISPackagePublishing project in the Power BI folder of the SSIS Catalog. This query uses the linked server named  [Default Linked Server for Integration Services] that in turn uses the new OLE DB Provider for SSIS. The query includes folder name, project name, and package name in the SSIS catalog. The OLE DB Provider for SSIS runs the package you specified in the query and returns the tabular result set.  
 
-```  
+```sql
 SELECT * FROM OPENQUERY([Default Linked Server for Integration Services], N'Folder=Power BI;Project=SSISPackagePublishing;Package=Package.dtsx')  
 
 ```  

docs/integration-services/extending-packages-custom-objects/building-deploying-and-debugging-custom-objects.md

@@ -1,25 +1,25 @@
----
-title: "Building, Deploying, and Debugging Custom Objects | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/14/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "docset-sql-devref"
-ms.tgt_pltfrm: ""
-ms.topic: "reference"
-applies_to: 
-  - "SQL Server 2016 Preview"
-helpviewer_keywords: 
-  - "custom objects [Integration Services]"
-ms.assetid: b03685bc-5398-4c3f-901a-1219c1098fbe
-caps.latest.revision: 50
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Building, Deploying, and Debugging Custom Objects
+---
+title: "Building, Deploying, and Debugging Custom Objects | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/14/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "docset-sql-devref"
+ms.tgt_pltfrm: ""
+ms.topic: "reference"
+applies_to: 
+  - "SQL Server 2016 Preview"
+helpviewer_keywords: 
+  - "custom objects [Integration Services]"
+ms.assetid: b03685bc-5398-4c3f-901a-1219c1098fbe
+caps.latest.revision: 50
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Building, Deploying, and Debugging Custom Objects
   After you have written the code for a custom object for [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], you must build the assembly, deploy it, and integrate it into [!INCLUDE[ssIS](../../includes/ssis-md.md)] Designer to make it available for use in packages, and test and debug it.  
 
 ##  <a name="top"></a> Steps in Building, Deploying, and Debugging a Custom Object for Integration Services  
@@ -65,7 +65,7 @@ manager: "jhubbard"
 
  Here is an example of a post-build event command line for a custom log provider:  
 
-```  
+```cmd
 "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools\gacutil.exe" -u $(TargetName)  
 "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools\gacutil.exe" -i $(TargetFileName)  
 copy $(TargetFileName) "C:\Program Files\Microsoft SQL Server\130\DTS\LogProviders "  

docs/integration-services/extending-packages-scripting-data-flow-script-component-examples/parsing-non-standard-text-file-formats-with-the-script-component.md

@@ -1,28 +1,28 @@
----
-title: "Parsing Non-Standard Text File Formats with the Script Component | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/17/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "docset-sql-devref"
-ms.tgt_pltfrm: ""
-ms.topic: "reference"
-applies_to: 
-  - "SQL Server 2016 Preview"
-helpviewer_keywords: 
-  - "text file reading [Integration Services]"
-  - "Script component [Integration Services], non-standard text file formats"
-  - "transformations [Integration Services], components"
-  - "Script component [Integration Services], examples"
-ms.assetid: 1fda034d-09e4-4647-9a9f-e8d508c2cc8f
-caps.latest.revision: 36
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Parsing Non-Standard Text File Formats with the Script Component
+---
+title: "Parsing Non-Standard Text File Formats with the Script Component | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/17/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "docset-sql-devref"
+ms.tgt_pltfrm: ""
+ms.topic: "reference"
+applies_to: 
+  - "SQL Server 2016 Preview"
+helpviewer_keywords: 
+  - "text file reading [Integration Services]"
+  - "Script component [Integration Services], non-standard text file formats"
+  - "transformations [Integration Services], components"
+  - "Script component [Integration Services], examples"
+ms.assetid: 1fda034d-09e4-4647-9a9f-e8d508c2cc8f
+caps.latest.revision: 36
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Parsing Non-Standard Text File Formats with the Script Component
   When your source data is arranged in a non-standard format, you may find it more convenient to consolidate all your parsing logic in a single script than to chain together multiple [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] transformations to achieve the same result.  
 
  [Example 1: Parsing Row-Delimited Records](#example1)  
@@ -66,7 +66,7 @@ manager: "jhubbard"
   
 3.  Select a destination database, and open a new query window. In the query window, execute the following script to create the destination table:  
   
-    ```  
+    ```sql
     create table RowDelimitedData  
     (  
     FirstName varchar(32),  
@@ -220,7 +220,7 @@ public override void Input0_ProcessInputRow(Input0Buffer Row)
   
 3.  Select a destination database, and open a new query window. In the query window, execute the following script to create the destination tables:  
   
-    ```  
+    ```sql
     CREATE TABLE [dbo].[Parents]([ParentID] [int] NOT NULL,  
     [ParentRecord] [varchar](32) NOT NULL,  
      CONSTRAINT [PK_Parents] PRIMARY KEY CLUSTERED   

docs/integration-services/extending-packages-scripting-data-flow-script-component-types/creating-a-source-with-the-script-component.md

@@ -1,29 +1,29 @@
----
-title: "Creating a Source with the Script Component | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/17/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "docset-sql-devref"
-ms.tgt_pltfrm: ""
-ms.topic: "reference"
-applies_to: 
-  - "SQL Server 2016 Preview"
-dev_langs: 
-  - "VB"
-helpviewer_keywords: 
-  - "Script component [Integration Services], source components"
-  - "output columns [Integration Services]"
-  - "sources [Integration Services], components"
-ms.assetid: 547c4179-ea82-4265-8c6f-04a2aa77a3c0
-caps.latest.revision: 59
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Creating a Source with the Script Component
+---
+title: "Creating a Source with the Script Component | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/17/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "docset-sql-devref"
+ms.tgt_pltfrm: ""
+ms.topic: "reference"
+applies_to: 
+  - "SQL Server 2016 Preview"
+dev_langs: 
+  - "VB"
+helpviewer_keywords: 
+  - "Script component [Integration Services], source components"
+  - "output columns [Integration Services]"
+  - "sources [Integration Services], components"
+ms.assetid: 547c4179-ea82-4265-8c6f-04a2aa77a3c0
+caps.latest.revision: 59
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Creating a Source with the Script Component
   You use a source component in the data flow of an [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] package to load data from a data source to pass on to downstream transformations and destinations. Ordinarily you connect to the data source through an existing connection manager.  
 
  For an overview of the Script component, see [Extending the Data Flow with the Script Component](../../integration-services/extending-packages-scripting/data-flow-script-component/extending-the-data-flow-with-the-script-component.md).  
@@ -136,7 +136,7 @@ manager: "jhubbard"
 
 6.  Create and configure a destination component, such as a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] destination, or the sample destination component demonstrated in [Creating a Destination with the Script Component](../../integration-services/extending-packages-scripting-data-flow-script-component-types/creating-a-destination-with-the-script-component.md), that expects the **AddressID** and **City** columns. Then connect the source component to the destination. (You can connect a source directly to a destination without any transformations.) You can create a destination table by running the following [!INCLUDE[tsql](../../includes/tsql-md.md)] command in the **AdventureWorks** database:  
 
-    ```  
+    ```sql
     CREATE TABLE [Person].[Address2]([AddressID] [int] NOT NULL,  
         [City] [nvarchar](30) NOT NULL)  
     ```  
@@ -269,7 +269,7 @@ manager: "jhubbard"
 
 7.  Create and configure a destination component, such as a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] destination, or the sample destination component demonstrated in [Creating a Destination with the Script Component](../../integration-services/extending-packages-scripting-data-flow-script-component-types/creating-a-destination-with-the-script-component.md). Then connect the source component to the destination. (You can connect a source directly to a destination without any transformations.) You can create a destination table by running the following [!INCLUDE[tsql](../../includes/tsql-md.md)] command in the **AdventureWorks** database:  
 
-    ```  
+    ```sql
     CREATE TABLE [Person].[Address2]([AddressID] [int] NOT NULL,  
         [City] [nvarchar](30) NOT NULL)  
     ```  
@@ -390,4 +390,4 @@ manager: "jhubbard"
  [Creating a Destination with the Script Component](../../integration-services/extending-packages-scripting-data-flow-script-component-types/creating-a-destination-with-the-script-component.md)   
  [Developing a Custom Source Component](../../integration-services/extending-packages-custom-objects-data-flow-types/developing-a-custom-source-component.md)  
 
-  
+  

docs/integration-services/import-export-data/connect-to-a-sql-server-data-source-sql-server-import-and-export-wizard.md

@@ -92,18 +92,18 @@ Specify **Trusted_Connection=Yes** to connect with Windows integrated authentica
 ### Connection string format
 Here's the format of a connection string that uses Windows integrated authentication.
 
-    Driver={ODBC Driver 13 for SQL Server};server=<server>;database=<database>;trusted_connection=Yes;
+    `Driver={ODBC Driver 13 for SQL Server};server=<server>;database=<database>;trusted_connection=Yes;`
 
 Here's the format of a connection string that uses SQL Server authentication instead of Windows integrated authentication.
 
-     Driver={ODBC Driver 13 for SQL Server};server=<server>;database=<database>;uid=<user id>;pwd=<password>;
+     `Driver={ODBC Driver 13 for SQL Server};server=<server>;database=<database>;uid=<user id>;pwd=<password>;`
 
 ### Enter the connection string
 Enter the connection string in the **ConnectionString** field, or enter the DSN name in the **Dsn** field, on the **Choose a Data Source** or **Choose a Destination** page. After you enter the connection string, the wizard parses the string and displays the individual properties and their values in the list.
 
 The following example uses this connection string.
 
-    Driver={ODBC Driver 13 for SQL Server};server=localhost;database=WideWorldImporters;trusted_connection=Yes;
+    `Driver={ODBC Driver 13 for SQL Server};server=localhost;database=WideWorldImporters;trusted_connection=Yes;`
 
 Here's the screen that you see after entering the connection string.
 

docs/integration-services/lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md

@@ -17,10 +17,9 @@ You can now move your SQL Server Integration Services (SSIS) packages and worklo
 
 ## Benefits
 Moving your on-premises SSIS workloads to Azure has the following potential benefits:
--   **Reduce operational costs** by reducing on-premises infrastructure.
--   **Increase high availability** with multiple nodes per cluster, as well as the high availability features of Azure and of Azure SQL Database.
+-   **Reduce operational costs** and reduce the burden of managing infrastructure that you have when you run SSIS on-premises or on Azure virtual machines.
+-   **Increase high availability** with the ability to specify multiple nodes per cluster, as well as the high availability features of Azure and of Azure SQL Database.
 -   **Increase scalability** with the ability to specify multiple cores per node (scale up) and multiple nodes per cluster (scale out).
--   **Avoid the limitations** of running SSIS on Azure virtual machines.
 
 ## Architecture overview
 The following table highlights the differences between SSIS on premises and SSIS on Azure. The most significant difference is the separation of storage from compute.

docs/integration-services/packages/legacy-package-deployment-ssis.md

@@ -150,7 +150,7 @@ manager: "jhubbard"
 
  The following SQL statement shows the default CREATE TABLE statement that the Package Configuration Wizard provides.  
 
-```  
+```sql
 CREATE TABLE [dbo].[SSIS Configurations]  
 (  
 ConfigurationFilter NVARCHAR(255) NOT NULL,  

docs/integration-services/performance/performance-counters.md

@@ -52,13 +52,13 @@ manager: "jhubbard"
 
  In the following example, the function returns statistics for a running execution with an ID of 34.  
 
-```  
+```sql
 select * from [catalog].[dm_execution_performance_counters] (34)  
 ```  
 
  In the following example, the function returns statistics for all the executions running on the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] server.  
 
-```  
+```sql
 select * from [catalog].[dm_execution_performance_counters] (NULL)  
 
 ```  

docs/integration-services/system-views/catalog-execution-component-phases.md

@@ -41,7 +41,7 @@ manager: "jhubbard"
 > [!WARNING]  
 >  The catalog.execution_component_phases view provides this information when the logging level of the package execution is set to Performance or Verbose. For more information, see [Enable Logging for Package Execution on the SSIS Server](../../integration-services/performance/integration-services-ssis-logging.md#server_logging).  
   
-```  
+```sql
 use SSISDB  
 select package_name, task_name, subcomponent_name, execution_path,  
     SUM(DATEDIFF(ms,start_time,end_time)) as active_time,  

docs/relational-databases/in-memory-oltp/atomic-blocks-in-native-procedures.md

@@ -1,7 +1,7 @@
 ---
 title: "Atomic Blocks | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/02/2016"
+ms.date: "10/26/2017"
 ms.prod: "sql-server-2016"
 ms.reviewer: ""
 ms.suite: ""
@@ -17,6 +17,8 @@ manager: "jhubbard"
 ms.workload: "Inactive"
 ---
 # Atomic Blocks in Native Procedures
+[!INCLUDE[tsql-appliesto-ss2014-asdb-xxxx-xxx_md](../../includes/tsql-appliesto-ss2014-asdb-xxxx-xxx-md.md)]
+
   **BEGIN ATOMIC** is part of the ANSI SQL standard. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports atomic blocks at the top-level of natively compiled stored procedures, as well as for natively compiled, scalar user-defined functions. For more information about these functions, see [Scalar User-Defined Functions for In-Memory OLTP](../../relational-databases/in-memory-oltp/scalar-user-defined-functions-for-in-memory-oltp.md).  
 
 -   Every natively compiled stored procedure contains exactly one block of [!INCLUDE[tsql](../../includes/tsql-md.md)] statements. This is an ATOMIC block.  
@@ -122,7 +124,7 @@ ORDER BY c1
 GO  
 ```  
 
- The following error messages specific to memory-optimized tables are transaction dooming. If they occur in the scope of an atomic block, they will cause the transaction to abort: 10772, 41301, 41302, 41305, 41325, 41332, and 41333.  
+ The following error messages specific to memory-optimized tables are transaction dooming. If they occur in the scope of an atomic block, they will cause the transaction to abort: 10772, 41301, 41302, 41305, 41325, 41332, 41333, and 41839.  
 
 ## Session Settings  
  The session settings in atomic blocks are fixed when the stored procedure is compiled. Some settings can be specified with **BEGIN ATOMIC** while other settings are always fixed to the same value.