Merge pull request #4823 from MSDN-WhiteKnight/patch-1

Format queries as code blocks

Author: MightyPen

docs/relational-databases/errors-events/mssqlserver-137-database-engine-error.md

@@ -29,12 +29,15 @@ ms.author: mathoma
 ## Explanation  
 This error occurs when a variable is used in a SQL script without first declaring the variable. The following example returns error 137 for both the SET and SELECT statements because **\@mycol** is not declared.  
 
+```sql
 SET @mycol = 'ContactName';  
 
-SELECT @mycol;  
+SELECT @mycol; 
+```
 
 One of the more complicated causes of this error includes the use of a variable that is declared outside the EXECUTE statement. For example, the variable **\@mycol** specified in the SELECT statement is local to the SELECT statement; thus it is outside the EXECUTE statement.  
 
+```sql
 USE AdventureWorks2012;  
 
 GO  
@@ -43,13 +46,15 @@ DECLARE @mycol nvarchar(20);
 
 SET @mycol = 'Name';  
 
-EXECUTE ('SELECT @mycol FROM Production.Product;');  
+EXECUTE ('SELECT @mycol FROM Production.Product;'); 
+```
 
 ## User Action  
 Verify that any variables used in a SQL script are declared before being used elsewhere in the script.  
 
 Rewrite the script so that it does not reference variables in the EXECUTE statement that are declared outside of it. For example:  
 
+```sql
 USE AdventureWorks2012;  
 
 GO  
@@ -58,7 +63,8 @@ DECLARE @mycol nvarchar(20) ;
 
 SET @mycol = 'Name';  
 
-EXECUTE ('SELECT ' + @mycol + ' FROM Production.Product';) ;  
+EXECUTE ('SELECT ' + @mycol + ' FROM Production.Product';) ;
+```
 
 ## See Also  
 [EXECUTE (Transact-SQL)](~/t-sql/language-elements/execute-transact-sql.md)  

docs/relational-databases/errors-events/mssqlserver-605-database-engine-error.md

@@ -48,6 +48,7 @@ If the 605 error is not transient, the problem is severe and must be corrected b
 
 1.  Identify the tables associated with the allocation units specified in the message by running the following query. Replace `allocation_unit_id` with the allocation units specified in the error message.  
 
+    ```sql  
     USE`database_name`;  
 
     GO  
@@ -67,6 +68,7 @@ If the 605 error is not transient, the problem is severe and must be corrected b
     ORDER BY au.allocation_unit_id;  
 
     GO  
+    ```
 
 2.  Execute DBCC CHECKTABLE without a REPAIR clause on the table associated with the second allocation unit ID specified in the error message.