Merge pull request #2667 from douglaslMS/cats-fixes-0728

v-shils · web-flow · commit 41a800eec8c9 · 2017-07-28T13:23:33.000-07:00
Fixed CATS QA issues, mostly missing language tags.
diff --git a/docs/integration-services/dtutil-utility.md b/docs/integration-services/dtutil-utility.md
@@ -75,8 +75,7 @@ manager: "jhubbard"
   
 ## Syntax  
   
-```  
-  
+```dos
 dtutil /option [value] [/option [value]]...  
 ```  
   
@@ -134,33 +133,33 @@ dtutil /option [value] [/option [value]]...
 ### Copy Examples  
  To copy a package that is stored in the **msdb** database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] using Windows Authentication to the SSIS Package Store, use the following syntax:  
   
-```  
+```dos
 dtutil /SQL srcPackage /COPY DTS;destFolder\destPackage   
 ```  
   
  To copy a package from a location on the File system to another location and give the copy a different name, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE c:\myPackages\mypackage.dtsx /COPY FILE;c:\myTestPackages\mynewpackage.dtsx  
 ```  
   
  To copy a package on the local file system to an instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] hosted on another computer, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE c:\sourcepkg.dtsx /DestServer <servername> /COPY SQL;destpkgname  
 ```  
   
  Because the */DestU[ser]* and */DestP[assword]* options were not used, Windows Authentication is assumed.  
   
  To create a new ID for a package after it is copied, use the following syntax:  
   
-```  
+```dos
 dtutil /I /FILE copiedpkg.dtsx   
 ```  
   
  To create a new ID for all the packages in a specific folder, use the following syntax:  
   
-```  
+```dos
 for %%f in (C:\test\SSISPackages\*.dtsx) do dtutil.exe /I /FILE %%f  
 ```  
   
@@ -169,13 +168,13 @@ for %%f in (C:\test\SSISPackages\*.dtsx) do dtutil.exe /I /FILE %%f
 ### Delete Examples  
  To delete a package that is stored in the **msdb** database on an instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses Windows Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /SQL delPackage /DELETE  
 ```  
   
  To delete a package that is stored in the **msdb** database on an instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /SQL delPackage /SOURCEUSER srcUserName /SOURCEPASSWORD #8nGs*w7F /DELETE  
 ```  
   
@@ -184,26 +183,26 @@ dtutil /SQL delPackage /SOURCEUSER srcUserName /SOURCEPASSWORD #8nGs*w7F /DELETE
   
  To delete a package that is stored in the SSIS Package Store, use the following syntax:  
   
-```  
+```dos
 dtutil /DTS delPackage.dtsx /DELETE  
 ```  
   
  To delete a package that is stored in the file system, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE c:\delPackage.dtsx /DELETE  
 ```  
   
 ### Exists Examples  
  To determine whether a package exists in the **msdb** database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses Windows Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /SQL srcPackage /EXISTS  
 ```  
   
  To determine whether a package exists in the **msdb** database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil SQL srcPackage /SOURCEUSER srcUserName /SOURCEPASSWORD *hY$d56b /EXISTS  
 ```  
   
@@ -212,26 +211,26 @@ dtutil SQL srcPackage /SOURCEUSER srcUserName /SOURCEPASSWORD *hY$d56b /EXISTS
   
  To determine whether a package exists in the local package store, use the following syntax:  
   
-```  
+```dos
 dtutil /DTS srcPackage.dtsx /EXISTS  
 ```  
   
  To determine whether a package exists in the local file system, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE c:\srcPackage.dtsx /EXISTS  
 ```  
   
 ### Move Examples  
  To move a package that is stored in the SSIS Package Store to the **msdb** database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses Windows Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /DTS srcPackage.dtsx /MOVE SQL;destPackage  
 ```  
   
  To move a package that is stored in the **msdb** database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication to the **msdb** database on another local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /SQL srcPackage /SOURCEUSER srcUserName /SOURCEPASSWORD $Hj45jhd@X /MOVE SQL;destPackage /DESTUSER destUserName /DESTPASSWORD !38dsFH@v  
 ```  
   
@@ -240,20 +239,20 @@ dtutil /SQL srcPackage /SOURCEUSER srcUserName /SOURCEPASSWORD $Hj45jhd@X /MOVE
   
  To move a package that is stored in the SSIS Package Store, use the following syntax:  
   
-```  
+```dos
 dtutil /DTS srcPackage.dtsx /MOVE DTS;destPackage.dtsx  
 ```  
   
  To move a package that is stored in the file system, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE c:\srcPackage.dtsx /MOVE FILE;c:\destPackage.dtsx  
 ```  
   
 ### Sign Examples  
  To sign a package that is stored in a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database on a local instance of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] that uses Windows Authentication, use the following syntax:  
   
-```  
+```dos
 dtutil /FILE srcPackage.dtsx /SIGN FILE;destpkg.dtsx;1767832648918a9d989fdac9819873a91f919  
 ```  
   
@@ -267,7 +266,7 @@ dtutil /FILE srcPackage.dtsx /SIGN FILE;destpkg.dtsx;1767832648918a9d989fdac9819
 ### Encrypt Examples  
  The following sample encrypts the file-based PackageToEncrypt.dtsx to the file-based EncryptedPackage.dts using full package encryption, with a password. The password that is used for the encryption is *EncPswd*.  
   
-```  
+```dos
 dtutil /FILE PackageToEncrypt.dtsx /ENCRYPT file;EncryptedPackage.dtsx;3;EncPswd  
 ```  
   
diff --git a/docs/integration-services/lesson-1-6-adding-and-configuring-the-lookup-transformations.md b/docs/integration-services/lesson-1-6-adding-and-configuring-the-lookup-transformations.md
@@ -1,23 +1,23 @@
----
-title: "Step 6: Adding and Configuring the Lookup Transformations | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/01/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "integration-services"
-ms.tgt_pltfrm: ""
-ms.topic: "get-started-article"
-applies_to: 
-  - "SQL Server 2016"
-ms.assetid: 5c59f723-9707-4407-80ae-f05f483cf65f
-caps.latest.revision: 38
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Lesson 1-6 - Adding and Configuring the Lookup Transformations
+---
+title: "Step 6: Adding and Configuring the Lookup Transformations | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/01/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "integration-services"
+ms.tgt_pltfrm: ""
+ms.topic: "get-started-article"
+applies_to: 
+  - "SQL Server 2016"
+ms.assetid: 5c59f723-9707-4407-80ae-f05f483cf65f
+caps.latest.revision: 38
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Lesson 1-6 - Adding and Configuring the Lookup Transformations
 After you have configured the Flat File source to extract data from the source file, the next task is to define the Lookup transformations needed to obtain the values for the **CurrencyKey** and **DateKey**. A Lookup transformation performs a lookup by joining data in the specified input column to a column in a reference dataset. The reference dataset can be an existing table or view, a new table, or the result of an SQL statement. In this tutorial, the Lookup transformation uses an OLE DB connection manager to connect to the database that contains the data that is the source of the reference dataset.  
   
 > [!NOTE]  
@@ -53,7 +53,7 @@ In both cases, the Lookup transformation will utilize the OLE DB connection mana
   
     2.  Select **Use results of an SQL query**, and then type or copy the following SQL statement:  
   
-        ```  
+        ```sql
         select * from (select * from [dbo].[DimCurrency]) as refTable  
         where [refTable].[CurrencyAlternateKey] = 'ARS'  
         OR  
diff --git a/docs/integration-services/lesson-4-3-adding-error-flow-redirection.md b/docs/integration-services/lesson-4-3-adding-error-flow-redirection.md
@@ -1,23 +1,23 @@
----
-title: "Step 3: Adding Error Flow Redirection | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/14/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "integration-services"
-ms.tgt_pltfrm: ""
-ms.topic: "get-started-article"
-applies_to: 
-  - "SQL Server 2016"
-ms.assetid: 5683a45d-9e73-4cd5-83ca-fae8b26b488c
-caps.latest.revision: 39
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Lesson 4-3 - Adding Error Flow Redirection
+---
+title: "Step 3: Adding Error Flow Redirection | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/14/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "integration-services"
+ms.tgt_pltfrm: ""
+ms.topic: "get-started-article"
+applies_to: 
+  - "SQL Server 2016"
+ms.assetid: 5683a45d-9e73-4cd5-83ca-fae8b26b488c
+caps.latest.revision: 39
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Lesson 4-3 - Adding Error Flow Redirection
 As demonstrated in the previous task, the Lookup Currency Key transformation cannot generate a match when the transformation tries to process the corrupted sample flat file, which produced an error. Because the transformation uses the default settings for error output, any error causes the transformation to fail. When the transformation fails, the rest of the package also fails.  
   
 Instead of permitting the transformation to fail, you can configure the component to redirect the failed row to another processing path by using the error output. Use of a separate error processing path lets you do a number of things. For instance, you might try to clean the data and then reprocess the failed row. Or, you might save the failed row along with additional error information for later verification and reprocessing.  
@@ -28,7 +28,7 @@ By default the two extra columns in an [!INCLUDE[ssISnoversion](../includes/ssis
   
 To enhance the usefulness of the error output, before the package writes the failed rows to the file, you will use a Script component to access the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] API and get a description of the error.  
   
-### To configure an error output  
+## To configure an error output  
   
 1.  In the **SSIS Toolbox**, expand **Common**, and then drag **Script Component** onto the design surface of the **Data Flow** tab. Place **Script** to the right of the **Lookup Currency Key** transformation.  
   
@@ -56,22 +56,22 @@ To enhance the usefulness of the error output, before the package writes the fai
   
     [Visual Basic]  
   
-    ```  
+    ```vb  
     Row.ErrorDescription =   
       Me.ComponentMetaData.GetErrorDescription(Row.ErrorCode)  
     ```  
   
     [Visual C#]  
   
-    ```  
+    ```cs
     Row.ErrorDescription = this.ComponentMetaData.GetErrorDescription(Row.ErrorCode);  
     ```  
   
     The completed subroutine will look like the following code.  
   
     [Visual Basic]  
   
-    ```  
+    ```vb
     Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)  
   
       Row.ErrorDescription =   
@@ -82,7 +82,7 @@ To enhance the usefulness of the error output, before the package writes the fai
   
     [Visual C#]  
   
-    ```  
+    ```cs
     public override void Input0_ProcessInputRow(Input0Buffer Row)  
         {  
   
diff --git a/docs/integration-services/service/integration-services-service-ssis-service.md b/docs/integration-services/service/integration-services-service-ssis-service.md
@@ -64,7 +64,8 @@ manager: "jhubbard"
   
  When you install the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] component of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is also installed. By default, the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is started and the startup type of the service is set to automatic. However, you must also install [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to use the service to manage stored and running [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages.  
   
-> **NOTE:** To connect directly to an instance of the legacy Integration Services Service, you have to use the version of SQL Server Management Studio (SSMS) aligned with the version of SQL Server on which the Integration Services Service is running. For example, to connect to the legacy Integration Services Service running on an instance of SQL Server 2016, you have to use the version of SSMS released for SQL Server 2016. [Download SQL Server Management Studio (SSMS)](https://msdn.microsoft.com/library/mt238290.aspx).
+> [!NOTE]
+> To connect directly to an instance of the legacy Integration Services Service, you have to use the version of SQL Server Management Studio (SSMS) aligned with the version of SQL Server on which the Integration Services Service is running. For example, to connect to the legacy Integration Services Service running on an instance of SQL Server 2016, you have to use the version of SSMS released for SQL Server 2016. [Download SQL Server Management Studio (SSMS)](https://msdn.microsoft.com/library/mt238290.aspx).
 >
 >   In the SSMS **Connect to Server** dialog box, you cannot enter the name of a server on which an earlier version of the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is running. However, to manage packages that are stored on a remote server, you do not have to connect to the instance of the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service on that remote server. Instead, edit the configuration file for the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service so that [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] displays the packages that are stored on the remote server.   
   
@@ -181,7 +182,7 @@ When you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)],
   
  **Example of a Default Configuration File**  
   
-```  
+```xml
 \<?xml version="1.0" encoding="utf-8"?>  
 \<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  
   <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>  
@@ -226,7 +227,7 @@ When you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)],
   
  **Example of a Modified Configuration File for a Named Instance of SQL Server**  
   
-```  
+```xml
 \<?xml version="1.0" encoding="utf-8"?>  
 \<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  
   <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>  
@@ -372,9 +373,17 @@ For more info, see [Getting Cross Domain Kerberos and Delegation working with SS
   
 #### To configure a Windows firewall using the Command Prompt window  
   
-1.  Run the command: `netsh firewall add portopening protocol=TCP port=135 name="RPC (TCP/135)" mode=ENABLE scope=SUBNET`  
+1.  Run the following command:
+
+    ```dos
+    netsh firewall add portopening protocol=TCP port=135 name="RPC (TCP/135)" mode=ENABLE scope=SUBNET
+    ```
   
-2.  Run the command: `netsh firewall add allowedprogram program="%ProgramFiles%\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe" name="SSIS Service" scope=SUBNET`  
+2.  Run the following command:
+
+    ```dos
+    netsh firewall add allowedprogram program="%ProgramFiles%\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe" name="SSIS Service" scope=SUBNET
+    ```
   
     > [!NOTE]  
     >  To open the firewall for all computers, and also for computers on the Internet, replace scope=SUBNET with scope=ALL.  
diff --git a/docs/relational-databases/json/import-json-documents-into-sql-server.md b/docs/relational-databases/json/import-json-documents-into-sql-server.md
@@ -73,13 +73,13 @@ You can also use OPENROWSET(BULK) as described above to read JSON files from oth
 
     Here is the command syntax:
 
-    ```
+    ```dos
     net use [drive letter] \\[storage name].file.core.windows.net\[share name] /u:[storage account name] [storage account access key]
     ```
 
     Here's an example that assigns local drive letter `T:` to the Azure File Storage share:
 
-    ```
+    ```dos
     net use t: \\mystorage.file.core.windows.net\sharejson /u:myaccount hb5qy6eXLqIdBj0LvGMHdrTiygkjhHDvWjUZg3Gu7bubKLg==
     ```
 
@@ -135,7 +135,7 @@ SELECT value
 ### Example 2
 OPENROWSET reads a single text value from the file, returns it as a BulkColumn, and passes it to the OPENJSON function. OPENJSON iterates through the array of JSON objects in the BulkColumn array and returns one book in each row, formatted as JSON:
 
-```
+```json
 {"id":"978-0641723445″, "cat":["book","hardcover"], "name":"The Lightning Thief", … 
 {"id":"978-1423103349″, "cat":["book","paperback"], "name":"The Sea of Monsters", … 
 {"id":"978-1857995879″, "cat":["book","paperback"], "name":"Sophie’s World : The Greek … 
@@ -160,7 +160,8 @@ In this example, OPENROWSET(BULK) reads the content of the file and passes that
 978-0641723445|The Lightning Thief|12.5|384|Rick Riordan| 
 978-1423103349|The Sea of Monsters|6.49|304|Rick Riordan| 
 978-1857995879|Sophie’s World : The Greek Philosophers|3.07|64|Jostein Gaarder| 
-978-1933988177|Lucene in Action, Second Edition|30.5|475|Michael McCandless| 
+978-1933988177|Lucene in Action, Second Edition|30.5|475|Michael McCandless|
+||||||
 
 Now you can return this table to the user, or load the data into another table.
 
