Merge pull request #19885 from arvindshmicrosoft/arvindsh/syntax-fixes-2

v-andreaco · web-flow · commit 93d53c5caf53 · 2021-08-05T17:48:45.000-06:00
Fix syntax errors in code samples
diff --git a/docs/relational-databases/errors-events/database-engine-events-and-errors.md b/docs/relational-databases/errors-events/database-engine-events-and-errors.md
@@ -22,7 +22,7 @@ SELECT message_id AS Error, severity AS Severity,
 [Event Logged] = CASE is_event_logged WHEN 0 THEN 'No' ELSE 'Yes' END,
 text AS [Description]
 FROM sys.messages
-WHERE language_id = <desired language, such as 1033 for US English>
+WHERE language_id = 1040 /* replace 1040 with the desired language ID, such as 1033 for US English*/
 ORDER BY message_id
 ```
 
diff --git a/docs/relational-databases/errors-events/mssqlserver-137-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-137-database-engine-error.md
@@ -64,7 +64,7 @@ DECLARE @mycol nvarchar(20) ;
   
 SET @mycol = 'Name';  
   
-EXECUTE ('SELECT ' + @mycol + ' FROM Production.Product';) ;
+EXECUTE ('SELECT ' + @mycol + ' FROM Production.Product;') ;
 ```
   
 ## See Also  
diff --git a/docs/relational-databases/errors-events/mssqlserver-17892-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-17892-database-engine-error.md
@@ -101,7 +101,7 @@ Another situation where log on triggers fail is when using the `EVENTDATA` funct
 User didn't maintain case when copying this script from the internet on this part of the trigger:
 
 ```sql
- SELECT EVENTDATA ().value ( '(/event_instance/clienthost)[1]' , 'NVARCHAR(15)' ));  
+ SELECT EVENTDATA().value ( '(/event_instance/clienthost)[1]' , 'NVARCHAR(15)');
 ```
 
 As a consequence, `EVENTDATA` always returned **NULL**, and all his SA equivalent logins were denied access. In this case, the DAC connection was not enabled, so we had no choice but to restart the server with the startup parameters listed above to drop the trigger.
diff --git a/docs/relational-databases/errors-events/mssqlserver-2814-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-2814-database-engine-error.md
@@ -55,10 +55,10 @@ The following table lists the reasons for recompilation.
         OBJECT_NAME(st.objectid) AS object_name,  
         st.text  
     FROM sys.dm_exec_query_stats AS qs  
-    CROSS APPLY sys.dm_exec_sql_text (*sql_handle*) AS st  
-    WHERE qs.statement_start_offset = *starting_offset*  
-    AND qs.statement_end_offset = *ending_offset*  
-    AND qs.plan_handle = *plan_handle*;
+    CROSS APPLY sys.dm_exec_sql_text (0x01000600B74C2A1300D2582A2100000000000000000000000000000000000000000000000000000000000000 /* replace the 0x01000600B... value with the actual sql_handle*/) AS st  
+    WHERE qs.statement_start_offset = 123 /*replace 123 with actual starting_offset value*/  
+    AND qs.statement_end_offset = 456 /*replace 456 with actual ending_offset value*/
+    AND qs.plan_handle = 0x06000100A27E7C1FA821B10600 /*replace 0x06000100A27E7C1FA821B10600with actual plan_handle value*/;
     ```
   
 2.  Based on the reason code description, modify the statement, batch, or procedure to avoid recompilations. For example, a stored procedure may contain one or more SET statements. These statements should be removed from the procedure. For additional examples of recompilation causes and resolutions, see [Batch Compilation, Recompilation, and Plan Caching Issues in SQL Server 2005](/previous-versions/sql/sql-server-2005/administrator/cc966425(v=technet.10)).  
diff --git a/docs/relational-databases/errors-events/mssqlserver-3988-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-3988-database-engine-error.md
@@ -49,5 +49,7 @@ In this situation, an attempt to run the query may raise either of the two error
 To work around the issue, enclose the distributed query in a 'begin distributed transaction' statement:
 
 ```sql
-BEGIN DISTRIBUTED TRANSACTION <Distributed Query> COMMIT TRANSACTION
+BEGIN DISTRIBUTED TRANSACTION
+/*The actual Distributed Query goes next, outside of comments*/
+COMMIT TRANSACTION
 ```
diff --git a/docs/relational-databases/errors-events/mssqlserver-3989-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-3989-database-engine-error.md
@@ -49,5 +49,7 @@ In this situation, an attempt to run the query may raise either of the two error
 To work around the issue, enclose the distributed query in a 'begin distributed transaction' statement:
 
 ```sql
-BEGIN DISTRIBUTED TRANSACTION <Distributed Query> COMMIT TRANSACTION
+BEGIN DISTRIBUTED TRANSACTION
+/*The actual Distributed Query goes next, outside of comments*/
+COMMIT TRANSACTION
 ```
diff --git a/docs/relational-databases/errors-events/mssqlserver-605-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-605-database-engine-error.md
@@ -64,7 +64,7 @@ If the 605 error is not transient, the problem is severe and must be corrected b
   
     JOIN sys.filegroups AS fg ON fg.data_space_id = au.data_space_id  
   
-    WHERE au.allocation_unit_id = `allocation_unit_id` OR au.allocation_unit_id = `allocation_unit_id`  
+    WHERE au.allocation_unit_id = '<allocation_unit_id>' OR au.allocation_unit_id = '<allocation_unit_id>'  
   
     ORDER BY au.allocation_unit_id;  
   
