Fix | Adding JAVA syntax highlight

ulvii · ulvii · commit 25c61788f47e · 2018-07-06T17:34:36.000-07:00
diff --git a/docs/connect/jdbc/accessing-diagnostic-information-in-the-extended-events-log.md b/docs/connect/jdbc/accessing-diagnostic-information-in-the-extended-events-log.md
@@ -29,7 +29,7 @@ manager: craigg
   
  The JDBC Driver also sends a thread-specific activity ID. The activity ID is captured in the extended events sessions if the sessions are started with the TRACK_CAUSAILITY option enabled. For performance issues with an active connection, you can get the activity ID from the client's trace (ActivityID field) and then locate the activity ID in the extended events output. The activity ID in extended events is a 16-byte GUID (not the same as the GUID for the client connection ID) appended with a four-byte sequence number. The sequence number represents the order of a request within a thread. The ActivityId is sent for SQL batch statements and RPC requests. To enable sending ActivityId to the server, you first need to specify the following key-value pair in the Logging.Properties file:  
   
-```  
+```java
 com.microsoft.sqlserver.jdbc.traceactivity = on  
 ```  
   
diff --git a/docs/connect/jdbc/always-encrypted-api-reference-for-the-jdbc-driver.md b/docs/connect/jdbc/always-encrypted-api-reference-for-the-jdbc-driver.md
@@ -160,7 +160,7 @@ New types in **microsoft.sql.Types** class
   
  **Syntax**  
   
-```  
+```java
 Public enum  SQLServerStatementColumnEncryptionSetting  
 ```  
   
diff --git a/docs/connect/jdbc/azure-key-vault-sample-version-6.0.0.md b/docs/connect/jdbc/azure-key-vault-sample-version-6.0.0.md
@@ -21,7 +21,7 @@ manager: craigg
 ##  Sample application using Azure Key Vault feature
 This application is runnable using JDBC Driver 6.0.0 and Azure-Keyvault (version 0.9.7),  Adal4j (version 1.3.0), and their dependencies.  The underlying dependencies can be resolved by adding these libraries to the pom file of the project as described [here](../../connect/jdbc/feature-dependencies-of-microsoft-jdbc-driver-for-sql-server.md): 
 
-```xml
+```java
 import java.net.URISyntaxException;
 import java.sql.Connection;
 import java.sql.DriverManager;
diff --git a/docs/connect/jdbc/azure-key-vault-sample-version-6.2.2.md b/docs/connect/jdbc/azure-key-vault-sample-version-6.2.2.md
@@ -21,7 +21,7 @@ manager: craigg
 ##  Sample application using Azure Key Vault feature
 This application is runnable using JDBC Driver 6.2.2 and above and Azure-Keyvault (version 1.0.0),  Adal4j (version 1.4.0), and their dependencies.  The underlying dependencies can be resolved by adding these libraries to the pom file of the project as described [here](../../connect/jdbc/feature-dependencies-of-microsoft-jdbc-driver-for-sql-server.md): 
 
-```xml
+```java
 import java.net.URISyntaxException;
 import java.sql.Connection;
 import java.sql.DriverManager;
diff --git a/docs/connect/jdbc/building-the-connection-url.md b/docs/connect/jdbc/building-the-connection-url.md
@@ -50,7 +50,7 @@ manager: craigg
   
  The following connection string shows an example of how to connect to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion_md.md)] database using integrated authentication and Kerberos from an application running on any operating system supported by the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)]:  
   
-```  
+```java
 jdbc:sqlserver://;servername=server_name;integratedSecurity=true;authenticationScheme=JavaKerberos  
 ```  
   
diff --git a/docs/connect/jdbc/configuring-how-java-sql-time-values-are-sent-to-the-server.md b/docs/connect/jdbc/configuring-how-java-sql-time-values-are-sent-to-the-server.md
@@ -54,7 +54,7 @@ manager: craigg
   
 Note that sendTimeAsDatetime must be false for encrypted columns as encrypted columns do not support the conversion from time to datetime. Beginning with Microsoft JDBC Driver 6.0 for SQL Server, the SQLServerConnection class has the following two methods to set/get the value of the sendTimeAsDatetime property.
 
-```
+```java
   public boolean getSendTimeAsDatetime()
   public void setSendTimeAsDatetime(boolean sendTimeAsDateTimeValue)
 ```
diff --git a/docs/connect/jdbc/connecting-to-an-azure-sql-database.md b/docs/connect/jdbc/connecting-to-an-azure-sql-database.md
@@ -79,7 +79,7 @@ shutdown /r /t 1
   
  For example:  
   
-```  
+```java
 jdbc:sqlserver://abcd.int.mscds.com;databaseName= myDatabase;user=myName;password=myPassword;encrypt=true;hostNameInCertificate= *.int.mscds.com;  
 ```  
   
diff --git a/docs/connect/jdbc/connecting-to-sql-server-with-the-jdbc-driver.md b/docs/connect/jdbc/connecting-to-sql-server-with-the-jdbc-driver.md
@@ -22,7 +22,7 @@ manager: craigg
   
  If a [!INCLUDE[ssNoVersion](../../includes/ssnoversion_md.md)] is only listening on an IPv6 port, set the java.net.preferIPv6Addresses system property to make sure that IPv6 is used instead of IPv4 to connect to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion_md.md)]:  
   
-```  
+```java
 System.setProperty("java.net.preferIPv6Addresses", "true");  
 ```  
   
diff --git a/docs/connect/jdbc/connecting-with-ssl-encryption.md b/docs/connect/jdbc/connecting-with-ssl-encryption.md
@@ -24,7 +24,7 @@ manager: craigg
   
  The following code example demonstrates how to set the **trustServerCertificate** property in a connection string:  
   
-```  
+```java
 String connectionUrl =   
     "jdbc:sqlserver://localhost:1433;" +  
      "databaseName=AdventureWorks;integratedSecurity=true;" +  
@@ -37,7 +37,7 @@ String connectionUrl =
   
  The following code example demonstrates how to set the **trustStore** and **trustStorePassword** properties in a connection string:  
   
-```  
+```java
 String connectionUrl =   
     "jdbc:sqlserver://localhost:1433;" +  
      "databaseName=AdventureWorks;integratedSecurity=true;" +  
@@ -49,7 +49,7 @@ String connectionUrl =
   
  The following code example demonstrates how to use the **hostNameInCertificate** property in a connection string:  
   
-```  
+```java
 String connectionUrl =   
     "jdbc:sqlserver://localhost:1433;" +  
      "databaseName=AdventureWorks;integratedSecurity=true;" +  
diff --git a/docs/connect/jdbc/fips-mode.md b/docs/connect/jdbc/fips-mode.md
@@ -36,12 +36,12 @@ Vendors may have some additional steps to configure JVM with FIPS.
 ### Ensure your JVM is in FIPS Mode
 In order to ensure your JVM is FIPS enabled, execute the following snippet: 
 
-````
+```java
 public boolean isFIPS() throws Exception {
     Provider jsse = Security.getProvider("SunJSSE");
     return jsse != null && jsse.getInfo().contains("FIPS");
 }
-````
+```
 
 ## Appropriate SSL Certificate
 In order to connect SQL Server in FIPS mode, a valid SSL Certificate is required. Install or import it in the Java Key Store on the client machine (JVM) where FIPS is enabled. If you did not import / install the appropriate certificate, you could not be able to connect to SQL Server as a secure connection cannot be made.
@@ -50,7 +50,7 @@ In order to connect SQL Server in FIPS mode, a valid SSL Certificate is required
 For FIPS, most likely you need to import the certificate (.cert) to either PKCS or in a provider-specific format. 
 Use the following snippet to import the SSL certificate and store it in a working directory with the appropriate KeyStore format. _TRUST_STORE_PASSWORD_ is your password for Java KeyStore. 
 
-````
+```java
 	public void saveGenericKeyStore(String provider, String trustStoreType, String certName, String certPath) throws KeyStoreException, CertificateException, NoSuchAlgorithmException, NoSuchProviderException, IOException {
 		KeyStore ks = KeyStore.getInstance(trustStoreType, provider);
 		FileOutputStream os = new FileOutputStream("./MyTrustStore_" + trustStoreType);
@@ -67,7 +67,7 @@ Use the following snippet to import the SSL certificate and store it in a workin
 		return cf.generateCertificate(fis);
 	}
 
-````
+```
 
 
 The following example is importing an Azure SSL Certificate in PKCS12 format with BouncyCastle Provider. The certificate is imported in the working directory named _MyTrustStore_PKCS12_ by using the following snippet:
diff --git a/docs/connect/jdbc/performing-batch-operations.md b/docs/connect/jdbc/performing-batch-operations.md
@@ -38,7 +38,7 @@ CREATE TABLE TestTable
   
  In the following example, an open connection to the [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal_md.md)] sample database is passed in to the function, the addBatch method is used to create the statements to be executed, and the executeBatch method is called to submit the batch to the database.  
   
-```  
+```java
 public static void executeBatchUpdate(Connection con) {  
    try {  
       Statement stmt = con.createStatement();  
diff --git a/docs/connect/jdbc/release-notes-for-the-jdbc-driver.md b/docs/connect/jdbc/release-notes-for-the-jdbc-driver.md
@@ -51,7 +51,7 @@ The JDBC Driver now supports sql_variant datatypes to be used with SQL Server. S
 
 1. For Date values:
 When using TVP to populate a table that contains datetime/smalldatetime/date values stored in sql_variant column, calling getDateTime()/getSmallDateTime()/getDate() methods on resultset does not work and throws the following exception:
-	```
+	```java
 	java.lang.String cannot be cast to java.sql.Timestamp
 	```
 	Workaround: use "getString()" or "getObject()" methods instead.
@@ -108,7 +108,7 @@ The Microsoft JDBC Driver 6.1 for SQL Server is fully compliant with JDBC specif
 The Microsoft JDBC Driver 6.0 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars contained in the 6.0 package are named according to their compliance with the JDBC API version. For example, the sqljdbc42.jar file from the 6.0 package is JDBC API 4.2 compliant. Similarly, the sqljdbc41.jar file is compliant with JDBC API 4.1.
 
 To ensure you have the right sqljdbc42.jar or sqljdbc41.jar, run the following lines of code. If the output is “Driver version: 6.0.7507.100“, you have the JDBC Driver 6.0 package.
-```
+```java
 Connection conn = DriverManager.getConnection("jdbc:sqlserver://<server>;user=<user>;password=<password>;");
 System.out.println("Driver version: " + conn.getMetaData().getDriverVersion());
 ```  
@@ -140,7 +140,7 @@ System.out.println("Driver version: " + conn.getMetaData().getDriverVersion());
 The Microsoft JDBC Driver 4.2 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars contained in the 4.2 package are named according to their compliance with the JDBC API version. For example, the sqljdbc42.jar file from the 4.2 package is JDBC API 4.2 compliant. Similarly, the sqljdbc41.jar file is compliant with JDBC API 4.1.
 
 To ensure you have the right sqljdbc42.jar or sqljdbc41.jar, run the following lines of code. If the output is "Driver version: 4.2.6420.100", you have the JDBC Driver 4.2 package.
-```
+```java
 Connection conn = DriverManager.getConnection("jdbc:sqlserver://<server>;user=<user>;password=<password>;");
 System.out.println("Driver version: " + conn.getMetaData().getDriverVersion());
 ```
diff --git a/docs/connect/jdbc/tracing-driver-operation.md b/docs/connect/jdbc/tracing-driver-operation.md
@@ -104,27 +104,27 @@ manager: craigg
 ## Enabling Tracing Programmatically  
  Tracing can be enabled programmatically by creating a Logger object and indicating the category to be logged. For example, the following code shows how to enable logging for SQL statements:  
   
-```  
+```java
 Logger logger = Logger.getLogger("com.microsoft.sqlserver.jdbc.Statement");  
 logger.setLevel(Level.FINER);  
 ```  
   
  To turn off logging in your code, use the following:  
   
-```  
+```java
 logger.setLevel(Level.OFF);  
 ```  
   
  To log all available categories, use the following:  
   
-```  
+```java
 Logger logger = Logger.getLogger("com.microsoft.sqlserver.jdbc");  
 logger.setLevel(Level.FINE);  
 ```  
   
  To disable a specific category from being logged, use the following:  
   
-```  
+```java
 Logger logger = Logger.getLogger("com.microsoft.sqlserver.jdbc.Statement");  
 logger.setLevel(Level.OFF);  
 ```  
diff --git a/docs/connect/jdbc/understanding-isolation-levels.md b/docs/connect/jdbc/understanding-isolation-levels.md
@@ -53,19 +53,19 @@ manager: craigg
   
  To set the isolation level for a transaction, you can use the [setTransactionIsolation](../../connect/jdbc/reference/settransactionisolation-method-sqlserverconnection.md) method of the [SQLServerConnection](../../connect/jdbc/reference/sqlserverconnection-class.md) class. This method accepts an **int** value as its argument, which is based on one of the connection constants as in the following:  
   
-```  
+```java
 con.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);  
 ```  
   
  To use the new snapshot isolation level of [!INCLUDE[ssNoVersion](../../includes/ssnoversion_md.md)], you can use one of the SQLServerConnection constants as in the following:  
   
-```  
+```java
 con.setTransactionIsolation(SQLServerConnection.TRANSACTION_SNAPSHOT);  
 ```  
   
  or you can use:  
   
-```  
+```java
 con.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED + 4094);  
 ```  
   
diff --git a/docs/connect/jdbc/understanding-java-ee-support.md b/docs/connect/jdbc/understanding-java-ee-support.md
@@ -50,7 +50,7 @@ manager: craigg
   
  The following shows how an application connects by using a data source:  
   
-```  
+```java
 initialize JNDI ..  
 Context ctx = new InitialContext(System.getProperties());  
 ...  
diff --git a/docs/connect/jdbc/understanding-xa-transactions.md b/docs/connect/jdbc/understanding-xa-transactions.md
@@ -43,7 +43,7 @@ manager: craigg
   
 -   A [SSTRANSTIGHTLYCPLD](../../connect/jdbc/reference/sstranstightlycpld-field-sqlserverxaresource.md) flag allows the applications to use tightly coupled XA transactions, which have different XA branch transaction IDs (BQUAL) but have the same global transaction ID (GTRID) and format ID (FormatID). In order to use that feature, you must set the [SSTRANSTIGHTLYCPLD](../../connect/jdbc/reference/sstranstightlycpld-field-sqlserverxaresource.md) on the flags parameter of the XAResource.start method:  
   
-    ```  
+    ```java
     xaRes.start(xid, SQLServerXAResource.SSTRANSTIGHTLYCPLD);  
     ```  
   
@@ -159,7 +159,7 @@ EXEC sp_addrolemember [SqlJDBCXAUser], 'shelby'
   
 ## Example  
   
-```  
+```java
 import java.net.Inet4Address;  
 import java.sql.*;  
 import java.util.Random;  
diff --git a/docs/connect/jdbc/using-advanced-data-types.md b/docs/connect/jdbc/using-advanced-data-types.md
@@ -49,7 +49,7 @@ manager: craigg
 ### Retrieving Large-Value Types from a Database  
  When you retrieve a non-binary large-value data type—such as the **varchar(max)** data type—from a database, one approach is to read that data as a character stream. In the following example, the [executeQuery](../../connect/jdbc/reference/executequery-method-sqlserverstatement.md) method of the [SQLServerStatement](../../connect/jdbc/reference/sqlserverstatement-class.md) class is used to retrieve data from the database and return it as a result set. Then the [getCharacterStream](../../connect/jdbc/reference/getcharacterstream-method-sqlserverresultset.md) method of the [SQLServerResultSet](../../connect/jdbc/reference/sqlserverresultset-class.md) class is used to read the large-value data from the result set.  
   
-```  
+```java
 ResultSet rs = stmt.executeQuery("SELECT TOP 1 * FROM Test1");  
 rs.next();  
 Reader reader = rs.getCharacterStream(2);  
@@ -60,15 +60,15 @@ Reader reader = rs.getCharacterStream(2);
   
  When you retrieve a binary large-value data type—such as the **varbinary(max)** data type—from a database, there are several approaches that you can take. The most efficient approach is to read the data as a binary stream, as in the following:  
   
-```  
+```java
 ResultSet rs = stmt.executeQuery("SELECT photo FROM mypics");  
 rs.next();  
 InputStream is = rs.getBinaryStream(2);  
 ```  
   
  You can also use the [getBytes](../../connect/jdbc/reference/getbytes-method-sqlserverresultset.md) method to read the data as a byte array, as in the following:  
   
-```  
+```java
 ResultSet rs = stmt.executeQuery("SELECT photo FROM mypics");  
 rs.next();  
 byte [] b = rs.getBytes(2);  
@@ -82,7 +82,7 @@ byte [] b = rs.getBytes(2);
   
  Using a String or bytes is also an option, as in the following:  
   
-```  
+```java
 PreparedStatement pstmt = con.prepareStatement("INSERT INTO test1 (c1_id, c2_vcmax) VALUES (?, ?)");  
 pstmt.setInt(1, 1);  
 pstmt.setString(2, htmlStr);  
@@ -94,7 +94,7 @@ pstmt.executeUpdate();
   
  If you have an image library on the server and must upload entire binary image files to a **varbinary(max)** column, the most efficient method with the JDBC driver is to use streams directly, as in the following:  
   
-```  
+```java
 PreparedStatement pstmt = con.prepareStatement("INSERT INTO test1 (Col1, Col2) VALUES(?,?)");  
 File inputFile = new File("CLOBFile20mb.jpg");  
 FileInputStream inStream = new FileInputStream(inputFile);  
@@ -113,7 +113,7 @@ inStream.close();
   
  If you have to replace the instance of a word in a large text file, such as an archived HTML file, you can use a Clob object, as in the following:  
   
-```  
+```java
 String SQL = "SELECT * FROM test1;";  
 Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);  
 ResultSet rs = stmt.executeQuery(SQL);  
diff --git a/docs/connect/jdbc/using-kerberos-integrated-authentication-to-connect-to-sql-server.md b/docs/connect/jdbc/using-kerberos-integrated-authentication-to-connect-to-sql-server.md
@@ -100,7 +100,7 @@ manager: craigg
   
  A login configuration file consists of one or more entries, each specifying which underlying authentication technology should be used for a particular application or applications. For example,  
   
-```  
+```java
 SQLJDBCDriver {  
    com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;  
 };  
@@ -166,7 +166,7 @@ Java.exe -Djava.security.auth.login.config=SQLJDBCDriver.conf -Djava.security.kr
 ## Constrained Delegation
 Beginning in Microsoft JDBC Driver 6.2, the driver supports Kerberos Constrained Delegation. The delegated credential can be passed in as org.ietf.jgss.GSSCredential object, these credentials are used by driver to establish connection. 
 
-```
+```java
 Properties driverProperties = new Properties();
 GSSCredential impersonatedUserCredential = [userCredential]
 driverProperties.setProperty("integratedSecurity", "true");
@@ -177,7 +177,7 @@ Connection conn = DriverManager.getConnection(CONNECTION_URI, driverProperties);
 
 ## Kerberos Connection using Principal Names and Password
 Beginning in Microsoft JDBC Driver 6.2, the driver can establish Kerberos connection using the Principal Name and Password passed in connection string. 
-```
+```java
 jdbc:sqlserver://servername=server_name;integratedSecurity=true;authenticationScheme=JavaKerberos;userName=user@REALM;password=****
 ```
 The username property does not require REALM if user belongs to the default_realm set in krb5.conf file. When `userName` and `password` is set along with `integratedSecurity=true;` and `authenticationScheme=JavaKerberos;` property, the connection is established with value of userName as Kerberos Principal along with the password supplied.
diff --git a/docs/connect/jdbc/using-sql-escape-sequences.md b/docs/connect/jdbc/using-sql-escape-sequences.md
@@ -46,7 +46,7 @@ manager: craigg
 ## LIKE Wildcard Literals  
  The JDBC driver supports the `{escape 'escape character'}` syntax for using LIKE clause wildcards as literals. For example, the following code will return values for col3, where the value of col2 literally begins with an underscore (and not its wildcard usage).  
   
-```  
+```java
 ResultSet rst = stmt.executeQuery("SELECT col3 FROM test1 WHERE col2   
 LIKE '\\_%' {escape '\\'}");  
 ```  
@@ -57,7 +57,7 @@ LIKE '\\_%' {escape '\\'}");
 ## Function Handling  
  The JDBC driver supports function escape sequences in SQL statements with the following syntax:  
   
-```  
+```java
 {fn functionName}  
 ```  
   
diff --git a/docs/connect/jdbc/using-table-valued-parameters.md b/docs/connect/jdbc/using-table-valued-parameters.md
diff --git a/docs/connect/jdbc/using-the-jdbc-driver.md b/docs/connect/jdbc/using-the-jdbc-driver.md
diff --git a/docs/connect/jdbc/working-with-a-connection.md b/docs/connect/jdbc/working-with-a-connection.md
diff --git a/docs/connect/jdbc/wrappers-and-interfaces.md b/docs/connect/jdbc/wrappers-and-interfaces.md
