Merge pull request #16139 from JKirsch1/revisedindentedcodeblocks1

v-dihans · web-flow · commit 1c46fe41b2bd · 2020-07-22T08:36:59.000-06:00
1750982 | Repairing indented code blocks | 1 revised
diff --git a/docs/relational-databases/in-memory-oltp/survey-of-initial-areas-in-in-memory-oltp.md b/docs/relational-databases/in-memory-oltp/survey-of-initial-areas-in-in-memory-oltp.md
@@ -326,8 +326,10 @@ SET @mesg = CONCAT(@LatestSalesOrderId,
 PRINT @mesg;  
 ```
       
-    -- Here is the actual PRINT output:  
-    -- 2 = Latest SalesOrderId, for CustomerId = 42  
+Here is the actual PRINT output:  
+```output
+-- 2 = Latest SalesOrderId, for CustomerId = 42  
+```
   
   
   
diff --git a/docs/relational-databases/replication/merge/specify-merge-replication-properties.md b/docs/relational-databases/replication/merge/specify-merge-replication-properties.md
@@ -163,8 +163,8 @@ This topic describes how to specify the conflict tracking and resolution level f
   
 At the Publisher on the publication database, execute [sp_addmergearticle &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-addmergearticle-transact-sql.md). Specify a value of **false** for `@delete_tracking`. For more information, see [Define an Article](../../../relational-databases/replication/publish/define-an-article.md).
   
-    > [!NOTE]  
-    >  If the source table for an article is already published in another publication, the value of **delete_tracking** must be the same for both articles.  
+> [!NOTE]  
+>  If the source table for an article is already published in another publication, the value of **delete_tracking** must be the same for both articles.  
   
 ### Specify that deletes be ignored for an existing merge article  
   
diff --git a/docs/relational-databases/replication/publish/create-an-updatable-subscription-to-a-transactional-publication.md b/docs/relational-databases/replication/publish/create-an-updatable-subscription-to-a-transactional-publication.md
@@ -95,7 +95,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
     * `sync tran` - enables the subscription for immediate updating.
     * `failover` - enables the subscription for immediate updating with queued updating as a failover option.
     > [!NOTE]  
->  `failover` requires that the publication also be enabled for queued updating subscriptions. 
+    >  `failover` requires that the publication also be enabled for queued updating subscriptions. 
  
 4. At the Subscriber, execute [sp_addpullsubscription_agent](../../../relational-databases/system-stored-procedures/sp-addpullsubscription-agent-transact-sql.md). Specify the following:
 
@@ -144,7 +144,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
     * The Windows credentials under which the Distribution Agent at the Distributor runs for `@job_login` and `@job_password`. 
 
     > [!NOTE]  
->  Connections made using Windows Integrated Authentication are always made using the Windows credentials specified by `@job_login` and `@job_password`. The Distribution Agent always makes the local connection to the Distributor using Windows Integrated Authentication. By default, the agent will connect to the Subscriber using Windows Integrated Authentication. 
+    >  Connections made using Windows Integrated Authentication are always made using the Windows credentials specified by `@job_login` and `@job_password`. The Distribution Agent always makes the local connection to the Distributor using Windows Integrated Authentication. By default, the agent will connect to the Subscriber using Windows Integrated Authentication. 
 
     * (Optional) A value of `0` for `@subscriber_security_mode` and the SQL Server login information for `@subscriber_login` and `@subscriber_password`, if you need to use SQL Server Authentication when connecting to the Subscriber. 
     * A schedule for the Distribution Agent job for this subscription.
@@ -174,7 +174,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
     * `queued failover` - enables support for queued updating with immediate updating as a failover option.
 
     > [!NOTE]  
->  `queued failover` requires that the publication also be enabled for immediate updating subscriptions. To fail over to immediate updating, you must use [sp_link_publication](../../../relational-databases/system-stored-procedures/sp-link-publication-transact-sql.md) to define the credentials under which changes at the Subscriber are replicated to the Publisher.
+    >  `queued failover` requires that the publication also be enabled for immediate updating subscriptions. To fail over to immediate updating, you must use [sp_link_publication](../../../relational-databases/system-stored-procedures/sp-link-publication-transact-sql.md) to define the credentials under which changes at the Subscriber are replicated to the Publisher.
  
 4. At the Subscriber, execute [sp_addpullsubscription_agent](../../../relational-databases/system-stored-procedures/sp-addpullsubscription-agent-transact-sql.md). Specify the following parameters:
 
diff --git a/docs/relational-databases/security/encryption/always-encrypted-query-columns-ads.md b/docs/relational-databases/security/encryption/always-encrypted-query-columns-ads.md
@@ -189,13 +189,15 @@ SELECT * FROM [dbo].[Patients]
 WHERE [SSN] = @SSN;
 ```
 
-    Msg 402, Level 16, State 2, Line 5   
-    The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC', 
-    encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
-    column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2' 
-    and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC', 
-    encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
-    column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator. 
+```output
+Msg 402, Level 16, State 2, Line 5   
+The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC', 
+encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
+column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2' 
+and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC', 
+encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
+column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
+```
 
 > [!NOTE]
 > Without parameterization, the entire query, including type conversions is processed inside SQL Server/Azure SQL Database. With parameterization enabled, some type conversions are performed by Microsoft .NET Data Provider for SQL Server inside Azure Data Studio. Due to differences between the Microsoft .NET type system and the SQL Server type system (for example, different precision of some types, such as float), a query executed with parameterization enabled can produce different results than the query executed without parameterization enabled. 
diff --git a/docs/relational-databases/security/encryption/always-encrypted-query-columns-ssms.md b/docs/relational-databases/security/encryption/always-encrypted-query-columns-ssms.md
@@ -198,13 +198,15 @@ SELECT * FROM [dbo].[Patients]
 WHERE [SSN] = @SSN;
 ```
 
-    Msg 402, Level 16, State 2, Line 5   
-    The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC', 
-    encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
-    column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2' 
-    and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC', 
-    encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
-    column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator. 
+```output
+Msg 402, Level 16, State 2, Line 5   
+The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC', 
+encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
+column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2' 
+and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC', 
+encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', 
+column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
+```
 
 > [!NOTE]
 > Without parameterization, the entire query, including type conversions, is processed inside SQL Server/Azure SQL Database. With parameterization enabled, some type conversions are performed by .NET Framework inside SQL Server Management Studio. Due to differences between the .NET Framework type system and the SQL Server type system (e.g. different precision of some types, such as float), a query executed with parameterization enabled can produce different results than the query executed without parameterization enabled. 
diff --git a/docs/relational-databases/system-dynamic-management-views/sys-dm-exec-sql-text-transact-sql.md b/docs/relational-databases/system-dynamic-management-views/sys-dm-exec-sql-text-transact-sql.md
@@ -104,7 +104,7 @@ Execute the following T-SQL in a new query window in [!INCLUDE[ssManStudioFull](
         WAITFOR DELAY '00:02:00';
       ```
       
-    2.  Using **CROSS APPLY**.  
+  2.  Using **CROSS APPLY**.  
     The sql_handle from **sys.dm_exec_requests** will be passed to **sys.dm_exec_sql_text** using **CROSS APPLY**. Open a new query window and pass the spid identified in step 1. In this example the spid happens to be `59`.
 
         ```sql
@@ -114,7 +114,7 @@ Execute the following T-SQL in a new query window in [!INCLUDE[ssManStudioFull](
         WHERE session_id = 59 -- modify this value with your actual spid
          ```      
  
-    2.  Passing **sql_handle** directly.  
+  2.  Passing **sql_handle** directly.  
 Acquire the **sql_handle** from **sys.dm_exec_requests**. Then, pass the **sql_handle** directly to **sys.dm_exec_sql_text**. Open a new query window and pass the spid identified in step 1 to **sys.dm_exec_requests**. In this example the spid happens to be `59`. Then pass the returned **sql_handle** as an argument to **sys.dm_exec_sql_text**.
 
         ```sql
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started.md
@@ -246,9 +246,9 @@ The Report Viewer Control is now shipped as a NuGet package and no longer shows
     
 The viewer control is designed for modern browsers. The control may not work as expected if the browser renders the page using IE compatibility mode. Intranet sites may require a meta tag to override default browser behavior.
 
-    ```
-    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
-    ```
+```html
+<meta http-equiv="X-UA-Compatible" content="IE=edge" />
+```
 
 ## NuGet.org pages
 
diff --git a/docs/reporting-services/install-windows/add-an-additional-report-server-to-a-farm-ssrs-scale-out.md b/docs/reporting-services/install-windows/add-an-additional-report-server-to-a-farm-ssrs-scale-out.md
@@ -68,7 +68,9 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
   
  If you configure all report servers with \<IsWebServiceEnable> set to False, you will see an error message similar to the following when you try to use [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] features:  
   
-      The Reporting Services Web Service is not enabled. Configure at least one instance of the Reporting Services SharePoint Service to have <IsWebServiceEnable> set to true. 
+```output
+The Reporting Services Web Service is not enabled. Configure at least one instance of the Reporting Services SharePoint Service to have <IsWebServiceEnable> set to true.
+```
  
  For more information, see [Modify a Reporting Services Configuration File &#40;RSreportserver.config&#41;](../../reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config.md)  
 
diff --git a/docs/reporting-services/install-windows/install-the-first-report-server-in-sharepoint-mode.md b/docs/reporting-services/install-windows/install-the-first-report-server-in-sharepoint-mode.md
@@ -87,13 +87,17 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
     > [!NOTE]
     > Make sure you specify the correct name of the SharePoint server.
     
-        Set-SPServer SERVERNAME -Role Custom
+    ```powershell
+    Set-SPServer SERVERNAME -Role Custom
+    ```
 
 4. You should see a response that a timer job was scheduled. You will need to wait for the job to execute.
 
 5. Use the following command to verify the server's assigned role.
 
-        Get-SPServer SERVERNAME 
+    ```powershell
+    Get-SPServer SERVERNAME 
+    ```
  
  6. The **Role** should list **Custom**.
  
@@ -204,7 +208,9 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
     > [!IMPORTANT]
     > If you see an error message similar to the following:  
     >   
+    ```powershell
     >     Install-SPRSService : The term 'Install-SPRSService' **is not recognized** as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.  
+    ```
     >
     > Either you are in the Windows Powershell instead of the SharePoint Management Shell  or Reporting Services SharePoint mode is not installed. For more information on Reporting Services and PowerShell, see [PowerShell cmdlets for Reporting Services SharePoint Mode](../../reporting-services/report-server-sharepoint/powershell-cmdlets-for-reporting-services-sharepoint-mode.md).  
   
diff --git a/docs/reporting-services/mobile-reports/prepare-data-for-reporting-services-mobile-reports.md b/docs/reporting-services/mobile-reports/prepare-data-for-reporting-services-mobile-reports.md
@@ -18,14 +18,15 @@ ms.author: maggies
 ## Date and time formats 
 When dealing with date and time intervals for use in a mobile report, particularly with the TimeNavigator, it's important to format the date/time column properly so the [!INCLUDE[PRODUCT_NAME](../../includes/ss-mobilereptpub-short.md)] can identify it as such. Here are examples of valid date/time formats:  
   
-    05/01/2009    
-    2009-05-01    
-    05/01/2009 14:57:32.8    
-    2009-05-01 14:57:32.8    
-    2009-05-01T14:57:32.8375298-04:00    
-    5/01/2008 14:57:32.80 -07:00    
-    1 May 2008 2:57:32.8 PM    
-    Fri, 15 May 2009 20:10:57 GMT    
+`05/01/2009`    
+`2009-05-01`    
+`05/01/2009 14:57:32.8`    
+`2009-05-01 14:57:32.8`    
+`2009-05-01T14:57:32.8375298-04:00`    
+`5/01/2008 14:57:32.80 -07:00`    
+`1 May 2008 2:57:32.8 PM`    
+`Fri, 15 May 2009 20:10:57 GMT`    
+
   
 Date- and time-based datasets can, in most cases, be described by one or more date/time intervals, such as hourly, daily, monthly, quarterly, and yearly. [!INCLUDE[PRODUCT_NAME](../../includes/ss-mobilereptpub-short.md)] can combine multiple tables of different granularity and display them on a single mobile report. However, keep in mind the relevant intervals from the original dataset(s), as they can help when deciding what date/time filter options to present to the user in the final mobile report.  
 
diff --git a/docs/reporting-services/mobile-reports/prepare-excel-data-for-reporting-services-mobile-reports.md b/docs/reporting-services/mobile-reports/prepare-excel-data-for-reporting-services-mobile-reports.md
@@ -65,11 +65,11 @@ There are no restrictions on where you store Excel files you import into the [!I
   
 Date fields are essential to many mobile reports, so make cells are properly formatted as dates in Excel. In some cases this means a conversion is necessary. Here are examples of formulas for converting cells from text to dates in Excel.  
   
-    Week 24-2013=DATE(MID(A2,9,4),1,-2)-WEEKDAY(DATE(MID(A2,9,4),1,3))+MID(A2,6,2)*7  
-  
-    2013/03/21=DATEVALUE(A1)  
-  
-    2013-mar-12=DATEVALUE(RIGHT(A1,2)&"-"&MID(A1,6,3)&"-"&LEFT(A1,4))  
+`Week 24-2013=DATE(MID(A2,9,4),1,-2)-WEEKDAY(DATE(MID(A2,9,4),1,3))+MID(A2,6,2)*7`  
+
+`2013/03/21=DATEVALUE(A1)`  
+
+`2013-mar-12=DATEVALUE(RIGHT(A1,2)&"-"&MID(A1,6,3)&"-"&LEFT(A1,4))`  
   
 After you've converted the cells, you have to format them as dates by selecting them, or the entire column > **Context** menu > **Format Cells** > **Date** from the **Category** list. You can also use the Excel text-to-columns wizard to convert text cells to properly formatted dates.  
   
diff --git a/docs/reporting-services/working-with-paginated-reports-web-portal.md b/docs/reporting-services/working-with-paginated-reports-web-portal.md
@@ -73,7 +73,7 @@ Specify a data processing extension that is used to process data from the data s
   
 Specify the connection string that the report server uses to connect to the data source. The connection type determines the syntax you should use. For example, a connection string for the XML data processing extension is a URL to an XML document. In most cases, a typical connection string specifies the database server and a data file. The following example illustrates a connection string used to connect to a SQL Server database that is named MyData:  
   
-    data source=(a SQL Server instance);initial catalog=MyData  
+`data source=(a SQL Server instance);initial catalog=MyData`
   
 A connection string can be configured as an expression so that you can specify the data source at run time. Data source expressions are defined in the report in Report Designer. Data source expressions cannot be defined, viewed, or modified in the web portal. However, you can replace a data source expression by clicking **Override Default** to type in a static connection string. If you want to switch back to the expression, click **Revert to Defaul**. The report server stores the original connection string in case you need to restore it. To use data source expressions, you must use the data source connection information that was originally published in the report. Shared data sources do not support the use of expressions in the connection string.  
   
diff --git a/docs/samples/wide-world-importers-generate-data.md b/docs/samples/wide-world-importers-generate-data.md
@@ -64,11 +64,11 @@ You can use the `Application.Configuration_PopulateLargeSaleTable` procedure to
 
 #### Name
 
-    Application.Configuration_PopulateLargeSaleTable
+`Application.Configuration_PopulateLargeSaleTable`
 
 #### Parameters
 
-  `@EstimatedRowsFor2012` **bigint** (with a default of 12000000)
+`@EstimatedRowsFor2012` **bigint** (with a default of 12000000)
 
 #### Result
 
diff --git a/docs/samples/wide-world-importers-oltp-install-configure.md b/docs/samples/wide-world-importers-oltp-install-configure.md
@@ -75,7 +75,9 @@ Applies to: SQL Server
 
 Enabling auditing in SQL Server requires server configuration. To enable SQL Server audit for the WideWorldImporters sample, run the following statement in the database:
 
-    EXECUTE [Application].[Configuration_ApplyAuditing]
+```sql
+EXECUTE [Application].[Configuration_ApplyAuditing]
+```
 
 In Azure SQL Database, Audit is configured through the [Azure portal](https://portal.azure.com/).
 
@@ -85,5 +87,7 @@ Applies to: Azure SQL Database
 
 Row-Level Security is not enabled by default in the bacpac download of WideWorldImporters. To enable Row-Level Security in the database, run the following stored procedure:
 
-    EXECUTE [Application].[Configuration_ApplyRowLevelSecurity]
+```sql
+EXECUTE [Application].[Configuration_ApplyRowLevelSecurity]
+```
 
diff --git a/docs/ssdt/how-to-change-target-platform-and-publish-a-database-project.md b/docs/ssdt/how-to-change-target-platform-and-publish-a-database-project.md
@@ -62,5 +62,5 @@ SSDT also makes this task simple by being aware of your target platform and auto
   
 **A project which specifies Microsoft SQL Server 2012 as the target platform may experience compatibility issues with SQL Server 2008**    If such project contains entities (for example, a Sequence object) that are introduced in Microsoft SQL Server 2012, the publishing operation will fail.  
   
-    The deployment will fail if object predicates use **CONTAINS** or **FREETEXT** over a newly created full-text index and transactional scripts are used. If the option to include transactional scripts is enabled during deployment, then procedures and views are defined inside a transaction while a full-text index is defined outside of a transaction at the end of the deploy script. Because of this ordering in the script, procedures or views using CONTAINS or FREETEXT will not be resolved against the full-text index, resulting in a deployment error.  
+The deployment will fail if object predicates use **CONTAINS** or **FREETEXT** over a newly created full-text index and transactional scripts are used. If the option to include transactional scripts is enabled during deployment, then procedures and views are defined inside a transaction while a full-text index is defined outside of a transaction at the end of the deploy script. Because of this ordering in the script, procedures or views using CONTAINS or FREETEXT will not be resolved against the full-text index, resulting in a deployment error.  
   
diff --git a/docs/ssma/db2/managing-passwords-db2tosql.md b/docs/ssma/db2/managing-passwords-db2tosql.md
diff --git a/docs/t-sql/statements/alter-login-transact-sql.md b/docs/t-sql/statements/alter-login-transact-sql.md
diff --git a/docs/t-sql/statements/create-external-file-format-transact-sql.md b/docs/t-sql/statements/create-external-file-format-transact-sql.md
