1741262 validation: code-block-indented

Author: TimShererWithAquent

articles/azure-monitor/app/asp-net-trace-logs.md

@@ -69,11 +69,15 @@ For examples of using the Application Insights ILogger implementation with conso
 ## Insert diagnostic log calls
 If you use System.Diagnostics.Trace, a typical call would be:
 
-    System.Diagnostics.Trace.TraceWarning("Slow response - database01");
+```csharp
+System.Diagnostics.Trace.TraceWarning("Slow response - database01");
+```
 
 If you prefer log4net or NLog, use:
 
+```csharp
     logger.Warn("Slow response - database01");
+```
 
 ## Use EventSource events
 You can configure [System.Diagnostics.Tracing.EventSource](https://msdn.microsoft.com/library/system.diagnostics.tracing.eventsource.aspx) events to be sent to Application Insights as traces. First, install the `Microsoft.ApplicationInsights.EventSourceListener` NuGet package. Then edit the `TelemetryModules` section of the [ApplicationInsights.config](../../azure-monitor/app/configuration-with-applicationinsights-config.md) file.
@@ -129,17 +133,21 @@ You can call the Application Insights trace API directly. The logging adapters u
 
 For example:
 
-    var telemetry = new Microsoft.ApplicationInsights.TelemetryClient();
-    telemetry.TrackTrace("Slow response - database01");
+```csharp
+var telemetry = new Microsoft.ApplicationInsights.TelemetryClient();
+telemetry.TrackTrace("Slow response - database01");
+```
 
 An advantage of TrackTrace is that you can put relatively long data in the message. For example, you can encode POST data there.
 
 You can also add a severity level to your message. And, like other telemetry, you can add property values to help filter or search for different sets of traces. For example:
 
-    var telemetry = new Microsoft.ApplicationInsights.TelemetryClient();
-    telemetry.TrackTrace("Slow database response",
-                   SeverityLevel.Warning,
-                   new Dictionary<string,string> { {"database", db.ID} });
+  ```csharp
+  var telemetry = new Microsoft.ApplicationInsights.TelemetryClient();
+  telemetry.TrackTrace("Slow database response",
+                 SeverityLevel.Warning,
+                 new Dictionary<string,string> { {"database", db.ID} });
+  ```
 
 This would enable you to easily filter out in [Search][diagnostic] all the messages of a particular severity level that relate to a particular database.
 

articles/azure-sql/database/elastic-query-horizontal-partitioning.md

@@ -43,10 +43,12 @@ These statements create the metadata representation of your sharded data tier in
 
 The credential is used by the elastic query to connect to your remote databases.  
 
+    ```sql
     CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password';
     CREATE DATABASE SCOPED CREDENTIAL <credential_name>  WITH IDENTITY = '<username>',  
     SECRET = '<password>'
     [;]
+    ```
 
 > [!NOTE]
 > Make sure that the *"\<username\>"* does not include any *"\@servername"* suffix.
@@ -55,6 +57,7 @@ The credential is used by the elastic query to connect to your remote databases.
 
 Syntax:
 
+    ```sql
     <External_Data_Source> ::=
     CREATE EXTERNAL DATA SOURCE <data_source_name> WITH
             (TYPE = SHARD_MAP_MANAGER,
@@ -63,9 +66,11 @@ Syntax:
             CREDENTIAL = <credential_name>,
             SHARD_MAP_NAME = ‘<shardmapname>’
                    ) [;]
+    ```
 
 ### Example
 
+    ```sql
     CREATE EXTERNAL DATA SOURCE MyExtSrc
     WITH
     (
@@ -75,10 +80,13 @@ Syntax:
         CREDENTIAL= SMMUser,
         SHARD_MAP_NAME='ShardMap'
     );
+    ```
 
 Retrieve the list of current external data sources:
 
+    ```sql
     select * from sys.external_data_sources;
+    ```
 
 The external data source references your shard map. An elastic query then uses the external data source and the underlying shard map to enumerate the databases that participate in the data tier.
 The same credentials are used to read the shard map and to access the data on the shards during the processing of an elastic query.
@@ -87,6 +95,7 @@ The same credentials are used to read the shard map and to access the data on th
 
 Syntax:  
 
+    ```sql
     CREATE EXTERNAL TABLE [ database_name . [ schema_name ] . | schema_name. ] table_name  
         ( { <column_definition> } [ ,...n ])
         { WITH ( <sharded_external_table_options> ) }
@@ -97,9 +106,11 @@ Syntax:
       [ SCHEMA_NAME = N'nonescaped_schema_name',]
       [ OBJECT_NAME = N'nonescaped_object_name',]
       DISTRIBUTION = SHARDED(<sharding_column_name>) | REPLICATED |ROUND_ROBIN
+    ```
 
 **Example**
 
+    ```sql
     CREATE EXTERNAL TABLE [dbo].[order_line](
          [ol_o_id] int NOT NULL,
          [ol_d_id] tinyint NOT NULL,
@@ -120,14 +131,17 @@ Syntax:
          OBJECT_NAME = 'order_details',
         DISTRIBUTION=SHARDED(ol_w_id)
     );
+    ```
 
 Retrieve the list of external tables from the current database:
 
     SELECT * from sys.external_tables;
 
 To drop external tables:
 
+    ```sql
     DROP EXTERNAL TABLE [ database_name . [ schema_name ] . | schema_name. ] table_name[;]
+    ```
 
 ### Remarks
 

articles/azure-sql/database/elastic-scale-split-merge-security-configuration.md

@@ -41,7 +41,10 @@ If those options are not available, you can generate **self-signed certificates*
 
     If installed, go to:
 
-        %ProgramFiles(x86)%\Windows Kits\x.y\bin\x86 
+    ```console
+    %ProgramFiles(x86)%\Windows Kits\x.y\bin\x86 
+    ```
+
 * Get the WDK from [Windows 8.1: Download kits and tools](https://msdn.microsoft.com/windows/hardware/gg454513#drivers)
 
 ## To configure the TLS/SSL certificate
@@ -187,12 +190,14 @@ This topic is for reference only. Follow the configuration steps outlined in:
 ## Create a self-signed certificate
 Execute:
 
+    ```console
     makecert ^
       -n "CN=myservice.cloudapp.net" ^
       -e MM/DD/YYYY ^
       -r -cy end -sky exchange -eku "1.3.6.1.5.5.7.3.1" ^
       -a sha256 -len 2048 ^
       -sv MySSL.pvk MySSL.cer
+    ```
 
 To customize:
 
@@ -203,7 +208,9 @@ To customize:
 ## Create PFX file for self-signed TLS/SSL certificate
 Execute:
 
-        pvk2pfx -pvk MySSL.pvk -spc MySSL.cer
+    ```console
+    pvk2pfx -pvk MySSL.pvk -spc MySSL.cer
+    ```
 
 Enter password and then export certificate with these options:
 
@@ -226,7 +233,9 @@ Upload certificate with the existing or generated .PFX file with the TLS key pai
 ## Update TLS/SSL certificate in service configuration file
 Update the thumbprint value of the following setting in the service configuration file with the thumbprint of the certificate uploaded to the cloud service:
 
+    ```console
     <Certificate name="SSL" thumbprint="" thumbprintAlgorithm="sha1" />
+    ```
 
 ## Import TLS/SSL certification authority
 Follow these steps in all account/machine that will communicate with the service:
@@ -254,13 +263,15 @@ Then, copy the same thumbprint as the TLS/SSL certificate in the CA certificate
 ## Create a self-signed certification authority
 Execute the following steps to create a self-signed certificate to act as a Certification Authority:
 
+    ```console
     makecert ^
     -n "CN=MyCA" ^
     -e MM/DD/YYYY ^
      -r -cy authority -h 1 ^
      -a sha256 -len 2048 ^
       -sr localmachine -ss my ^
       MyCA.cer
+    ```
 
 To customize it
 
@@ -307,13 +318,15 @@ Each individual authorized to access the service should have a client certificat
 
 The following steps must be executed in the same machine where the self-signed CA certificate was generated and stored:
 
+    ```console
     makecert ^
       -n "CN=My ID" ^
       -e MM/DD/YYYY ^
       -cy end -sky exchange -eku "1.3.6.1.5.5.7.3.2" ^
       -a sha256 -len 2048 ^
       -in "MyCA" -ir localmachine -is my ^
       -sv MyID.pvk MyID.cer
+    ```
 
 Customizing:
 
@@ -326,11 +339,15 @@ This command will prompt for a password to be created and then used once. Use a
 ## Create PFX files for client certificates
 For each generated client certificate, execute:
 
+    ```console
     pvk2pfx -pvk MyID.pvk -spc MyID.cer
+    ```
 
 Customizing:
 
+    ```console
     MyID.pvk and MyID.cer with the filename for the client certificate
+    ```
 
 Enter password and then export certificate with these options:
 
@@ -375,11 +392,15 @@ The default setting does not check with the Certification Authority for client c
 ## Create PFX file for self-signed encryption certificates
 For an encryption certificate, execute:
 
+    ```console
     pvk2pfx -pvk MyID.pvk -spc MyID.cer
+    ```
 
 Customizing:
 
+    ```console
     MyID.pvk and MyID.cer with the filename for the encryption certificate
+    ```
 
 Enter password and then export certificate with these options:
 

articles/azure-sql/database/elastic-scale-upgrade-client-library.md

@@ -53,6 +53,7 @@ Performing these steps in order ensures that old versions of the client library
 
 Alternatively, create a Visual Studio application that opens your ShardMapManager, iterates over all shards, and performs the metadata upgrade by calling the methods [UpgradeLocalStore](https://docs.microsoft.com/dotnet/api/microsoft.azure.sqldatabase.elasticscale.shardmanagement.shardmapmanager.upgradelocalstore) and [UpgradeGlobalStore](https://docs.microsoft.com/dotnet/api/microsoft.azure.sqldatabase.elasticscale.shardmanagement.shardmapmanager.upgradeglobalstore) as in this example:
 
+```cssharp
     ShardMapManager smm =
        ShardMapManagerFactory.GetSqlShardMapManager
        (connStr, ShardMapManagerLoadPolicy.Lazy);
@@ -63,6 +64,7 @@ Alternatively, create a Visual Studio application that opens your ShardMapManage
     {
        smm.UpgradeLocalStore(loc);
     }
+```
 
 These techniques for metadata upgrades can be applied multiple times without harm. For example, if an older client version inadvertently creates a shard after you have already updated, you can run upgrade again across all shards to ensure that the latest metadata version is present throughout your infrastructure.
 

articles/azure-sql/database/elastic-scale-working-with-dapper.md

@@ -81,6 +81,7 @@ The shard map object creates a connection to the shard that holds the shardlet f
 
 Queries work very much the same way - you first open the connection using [OpenConnectionForKey](https://msdn.microsoft.com/library/azure/dn807226.aspx) from the client API. Then you use the regular Dapper extension methods to map the results of your SQL query into .NET objects:
 
+```csharp
     using (SqlConnection sqlconn = shardingLayer.ShardMap.OpenConnectionForKey(
                     key: tenantId1,
                     connectionString: connStrBldr.ConnectionString,
@@ -98,6 +99,7 @@ Queries work very much the same way - you first open the connection using [OpenC
                 Console.WriteLine(item.Name);
             }
     }
+```
 
 Note that the **using** block with the DDR connection scopes all database operations within the block to the one shard where tenantId1 is kept. The query only returns blogs stored on the current shard, but not the ones stored on any other shards. 
 
@@ -106,6 +108,7 @@ Dapper comes with an ecosystem of additional extensions that can provide further
 
 Using DapperExtensions in your application does not change how database connections are created and managed. It is still the application’s responsibility to open connections, and regular SQL Client connection objects are expected by the extension methods. We can rely on the [OpenConnectionForKey](https://msdn.microsoft.com/library/azure/dn807226.aspx) as outlined above. As the following code samples show, the only change is that you no longer have to write the T-SQL statements:
 
+```csharp
     using (SqlConnection sqlconn = shardingLayer.ShardMap.OpenConnectionForKey(
                     key: tenantId2,
                     connectionString: connStrBldr.ConnectionString,
@@ -114,9 +117,11 @@ Using DapperExtensions in your application does not change how database connecti
            var blog = new Blog { Name = name2 };
            sqlconn.Insert(blog);
     }
+```
 
 And here is the code sample for the query: 
 
+```csharp
     using (SqlConnection sqlconn = shardingLayer.ShardMap.OpenConnectionForKey(
                     key: tenantId2,
                     connectionString: connStrBldr.ConnectionString,
@@ -130,12 +135,14 @@ And here is the code sample for the query:
                Console.WriteLine(item.Name);
            }
     }
+```
 
 ### Handling transient faults
 The Microsoft Patterns & Practices team published the [Transient Fault Handling Application Block](https://msdn.microsoft.com/library/hh680934.aspx) to help application developers mitigate common transient fault conditions encountered when running in the cloud. For more information, see [Perseverance, Secret of All Triumphs: Using the Transient Fault Handling Application Block](https://msdn.microsoft.com/library/dn440719.aspx).
 
 The code sample relies on the transient fault library to protect against transient faults. 
 
+```csharp
     SqlDatabaseUtils.SqlRetryPolicy.ExecuteAction(() =>
     {
        using (SqlConnection sqlconn =
@@ -145,6 +152,7 @@ The code sample relies on the transient fault library to protect against transie
               sqlconn.Insert(blog);
           }
     });
+```
 
 **SqlDatabaseUtils.SqlRetryPolicy** in the code above is defined as a **SqlDatabaseTransientErrorDetectionStrategy** with a retry count of 10, and 5 seconds wait time between retries. If you are using transactions, make sure that your retry scope goes back to the beginning of the transaction in the case of a transient fault.
 

articles/azure-sql/database/elastic-transactions-overview.md

@@ -44,6 +44,7 @@ Remember that elastic database transactions don't require installing MSDTC. Inst
 
 The following sample code uses the familiar programming experience with .NET System.Transactions. The TransactionScope class establishes an ambient transaction in .NET. (An “ambient transaction” is one that lives in the current thread.) All connections opened within the TransactionScope participate in the transaction. If different databases participate, the transaction is automatically elevated to a distributed transaction. The outcome of the transaction is controlled by setting the scope to complete to indicate a commit.
 
+```csharp
     using (var scope = new TransactionScope())
     {
         using (var conn1 = new SqlConnection(connStrDb1))
@@ -64,12 +65,14 @@ The following sample code uses the familiar programming experience with .NET Sys
 
         scope.Complete();
     }
+```
 
 ### Sharded database applications
 
 Elastic database transactions for SQL Database also support coordinating distributed transactions where you use the OpenConnectionForKey method of the elastic database client library to open connections for a scaled out data tier. Consider cases where you need to guarantee transactional consistency for changes across several different sharding key values. Connections to the shards hosting the different sharding key values are brokered using OpenConnectionForKey. In the general case, the connections can be to different shards such that ensuring transactional guarantees requires a distributed transaction.
 The following code sample illustrates this approach. It assumes that a variable called shardmap is used to represent a shard map from the elastic database client library:
 
+```csharp
     using (var scope = new TransactionScope())
     {
         using (var conn1 = shardmap.OpenConnectionForKey(tenantId1, credentialsStr))
@@ -90,6 +93,7 @@ The following code sample illustrates this approach. It assumes that a variable
 
         scope.Complete();
     }
+```
 
 ## .NET installation for Azure Cloud Services
 
@@ -99,6 +103,7 @@ For Azure App Service, upgrades to the guest OS are currently not supported. For
 
 Note that the installer for .NET 4.6.1 may require more temporary storage during the bootstrapping process on Azure cloud services than the installer for .NET 4.6. To ensure a successful installation, you need to increase temporary storage for your Azure cloud service in your ServiceDefinition.csdef file in the LocalResources section and the environment settings of your startup task, as shown in the following sample:
 
+```xml
     <LocalResources>
     ...
         <LocalStorage name="TEMP" sizeInMB="5000" cleanOnRoleRecycle="false" />
@@ -117,6 +122,7 @@ Note that the installer for .NET 4.6.1 may require more temporary storage during
             </Environment>
         </Task>
     </Startup>
+```
 
 ## Transactions across multiple servers