Merge pull request #8201 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/2014/relational-databases/extended-events/convert-an-existing-sql-trace-script-to-an-extended-events-session.md

@@ -34,7 +34,7 @@ manager: craigg
 
 2.  Obtain the ID of the trace. To do this, use the following query:  
 
-    ```  
+    ```sql
     SELECT * FROM sys.traces;  
     GO  
     ```  
@@ -49,7 +49,7 @@ manager: craigg
     > [!NOTE]  
     >  In this example, the trace ID for the default trace (1) is used.  
 
-    ```  
+    ```sql
     USE MASTER;  
     GO  
     DECLARE @trace_id int;  
@@ -76,7 +76,7 @@ manager: craigg
 
     3.  Use the following query to identify the correct data fields to use for the events that you identified in the previous step. The query shows the Extended Events data fields in the "event_field" column. In the query, replace *<event_name>* with the name of an event that you specified in the previous step.  
 
-        ```  
+        ```sql
         SELECT xp.name package_name, xe.name event_name  
            ,xc.name event_field, xc.description  
         FROM sys.trace_xe_event_map AS em  
@@ -97,7 +97,7 @@ manager: craigg
 
 1.  Add statements to create the event session, replacing s*ession_name* with the name that you want to use for the Extended Events session.  
 
-    ```  
+    ```sql
     IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
        DROP EVENT SESSION [Session_Name] ON SERVER;  
     CREATE EVENT SESSION [Session_Name]  
@@ -124,7 +124,7 @@ manager: craigg
 
      To convert this to the Extended Events equivalent, the sqlserver.sp_statement_starting and the sqlserver.sp_statement_completed events are added, with a list of actions. Predicate statements are included as WHERE clauses.  
 
-    ```  
+    ```sql
     ADD EVENT sqlserver.sp_statement_starting  
        (ACTION  
           (  
@@ -150,9 +150,9 @@ manager: craigg
        )  
     ```  
 
-3.  Add the asynchronous file target, replacing the file paths with the location where you want to save the ouput. When specifying the file target, you must include a log file and metadata file path file.  
+3.  Add the asynchronous file target, replacing the file paths with the location where you want to save the output. When specifying the file target, you must include a log file and metadata file path file.  
 
-    ```  
+    ```sql
     ADD TARGET package0.asynchronous_file_target(  
        SET filename='c:\temp\ExtendedEventsStoredProcs.xel', metadatafile='c:\temp\ExtendedEventsStoredProcs.xem');  
     ```  
@@ -161,7 +161,7 @@ manager: craigg
 
 1.  You can use the sys.fn_xe_file_target_read_file function to view the output. To do this, run the following query, replacing the file paths with the paths that you specified:  
 
-    ```  
+    ```sql
     SELECT *, CAST(event_data as XML) AS 'event_data_XML'  
     FROM sys.fn_xe_file_target_read_file('c:\temp\ExtendedEventsStoredProcs*.xel', 'c:\temp\ExtendedEventsStoredProcs*.xem', NULL, NULL);  
   
@@ -172,7 +172,7 @@ manager: craigg
 
      For more information about the sys.fn_xe_file_target_read_file function, see [sys.fn_xe_file_target_read_file &#40;Transact-SQL&#41;](/sql/relational-databases/system-functions/sys-fn-xe-file-target-read-file-transact-sql).  
 
-    ```  
+    ```sql
     IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
        DROP EVENT SESSION [session_name] ON SERVER;  
     CREATE EVENT SESSION [session_name]  
@@ -208,7 +208,7 @@ manager: craigg
 
 ## Example  
 
-```  
+```sql
 IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
    DROP EVENT SESSION [session_name] ON SERVER;  
 CREATE EVENT SESSION [session_name]  

docs/2014/sql-server/install/other-database-engine-upgrade-issues.md

@@ -58,7 +58,7 @@ manager: craigg
 -   HierarchyID  
 
 ## Target Table of the OUTPUT INTO Clause Cannot Have Any Defined Triggers  
- OUPUT INTO a target table when the table has any enabled triggers is not supported.  
+ OUTPUT INTO a target table when the table has any enabled triggers is not supported.  
 
 ## Compile Time Error for UDFs When the Target of an OUTPUT INTO Clause is a Table  
  User-defined functions (UDF) cannot be used to perform actions that modify the database state. For example, a UDF cannot perform any DDL (CREATE/ALTER/DROP) or DML (INSERT/UPDATE/DELETE) actions on any objects, except for table variables.  

docs/ado/reference/ado-api/parameters-collection-ado.md

@@ -39,7 +39,7 @@ Contains all the [Parameter](../../../ado/reference/ado-api/parameter-object.md)
 
 2.  When calling a stored procedure with parameters and explicitly appending a parameter to the **Parameters** collection with **Append**, the return value/output parameter should be appended to the **Parameters** collection. The return value must first be appended to the **Parameters** collection. Use **Append** to add the other parameters into the **Parameters** collection in the order of definition. For example, the stored procedure SPWithParam has two parameters. The first parameter, *InParam*, is an input parameter defined as adVarChar (20), and the second parameter, *OutParam*, is an output parameter defined as adVarChar (20). You can retrieve the return value/output parameter with the following code.  
 
-    ```  
+    ```vb
     ' Open Connection Conn  
     set ccmd = CreateObject("ADODB.Command")  
     ccmd.Activeconnection= Conn  
@@ -49,7 +49,7 @@ Contains all the [Parameter](../../../ado/reference/ado-api/parameter-object.md)
 
     ccmd.parameters.Append ccmd.CreateParameter(, adInteger, adParamReturnValue, , NULL)   ' return value  
     ccmd.parameters.Append ccmd.CreateParameter("InParam", adVarChar, adParamInput, 20, "hello world")   ' input parameter  
-    ccmd.parameters.Append ccmd.CreateParameter("OutParam", adVarChar, adParamOuput, 20, NULL)   ' output parameter  
+    ccmd.parameters.Append ccmd.CreateParameter("OutParam", adVarChar, adParamOutput, 20, NULL)   ' output parameter  
 
     ccmd.execute()  
 
@@ -60,7 +60,7 @@ Contains all the [Parameter](../../../ado/reference/ado-api/parameter-object.md)
 
 3.  When calling a stored procedure with parameters and configuring the parameters by calling the **Item** method on the **Parameters** collection, the return value/output parameter of the stored procedure can be retrieved from the **Parameters** collection. For example, the stored procedure SPWithParam has two parameters. The first parameter, *InParam*, is an input parameter defined as adVarChar (20), and the second parameter, *OutParam*, is an output parameter defined as adVarChar (20). You can retrieve the return value/output parameter with the following code.  
 
-    ```  
+    ```vb
     ' Open Connection Conn  
     set ccmd = CreateObject("ADODB.Command")  
     ccmd.Activeconnection= Conn  

docs/odbc/reference/odbc-64-bit-information.md

@@ -28,7 +28,7 @@ Beginning with Windows Server 2003, Microsoft operating systems have supported t
 ## Function Declaration Changes  
  The following function signatures have changed for 64-bit programming. The items in bold text are the specific parameters that are different.  
 
-```  
+```c
 SQLBindCol (SQLHSTMT StatementHandle, SQLUSMALLINT ColumnNumber,  
    SQLSMALLINT TargetType, SQLPOINTER TargetValuePtr, SQLLEN BufferLength,   SQLLEN * StrLen_or_Ind);  
 
@@ -109,7 +109,7 @@ SQLSetStmtOption (SQLHSTMT StatementHandle, SQLUSMALLINT Option,
 ## Changes in SQL Data Types  
  The following four SQL types are still supported on 32-bit only; they are not defined for 64-bit compilers. These types are no longer used for any parameters in MDAC 2.7; use of these types will cause compiler failures on 64-bit platforms.  
   
-```  
+```cpp
 #ifdef WIN32   
 typedef SQLULEN SQLROWCOUNT;   
 typedef SQLULEN SQLROWSETSIZE;   
@@ -120,7 +120,7 @@ typedef SQLLEN SQLROWOFFSET;
 
  The definition of SQLSETPOSIROW has changed for both 32-bit and 64-bit compilers:  
 
-```  
+```c
 #ifdef _WIN64   
 typedef UINT64 SQLSETPOSIROW;   
 #else   
@@ -130,7 +130,7 @@ typedef UINT64 SQLSETPOSIROW;
 
  The definitions of SQLLEN and SQLULEN have changed for 64-bit compilers:  
 
-```  
+```c
 #ifdef _WIN64   
 typedef INT64 SQLLEN;   
 typedef UINT64 SQLULEN;   
@@ -142,7 +142,7 @@ typedef UINT64 SQLULEN;
 
  Although SQL_C_BOOKMARK is deprecated in ODBC 3.0, for 64-bit compilers on 2.0 clients, this value has changed:  
 
-```  
+```c
 #ifdef _WIN64   
 #define SQL_C_BOOKMARK SQL_C_UBIGINT   
 #else   
@@ -152,7 +152,7 @@ typedef UINT64 SQLULEN;
 
  The BOOKMARK type is defined differently in the newer headers:  
 
-```  
+```c
 typedef SQLULEN BOOKMARK;  
 ```  
 
@@ -283,7 +283,7 @@ typedef SQLULEN BOOKMARK;
 
  SQL_DRIVER_HLIB  
 
- When *InfoType* has either of the following 2 values **InfoValuePtr* is 64-bits on both input and ouput:  
+ When *InfoType* has either of the following 2 values **InfoValuePtr* is 64-bits on both input and output:  
 
  SQL_DRIVER_HDESC  
 

docs/relational-databases/extended-events/convert-an-existing-sql-trace-script-to-an-extended-events-session.md

@@ -37,7 +37,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
 2.  Obtain the ID of the trace. To do this, use the following query:  
 
-    ```  
+    ```sql
     SELECT * FROM sys.traces;  
     GO  
     ```  
@@ -52,7 +52,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
     > [!NOTE]  
     >  In this example, the trace ID for the default trace (1) is used.  
 
-    ```  
+    ```sql
     USE MASTER;  
     GO  
     DECLARE @trace_id int;  
@@ -79,7 +79,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
     3.  Use the following query to identify the correct data fields to use for the events that you identified in the previous step. The query shows the Extended Events data fields in the "event_field" column. In the query, replace *<event_name>* with the name of an event that you specified in the previous step.  
 
-        ```  
+        ```sql
         SELECT xp.name package_name, xe.name event_name  
            ,xc.name event_field, xc.description  
         FROM sys.trace_xe_event_map AS em  
@@ -98,9 +98,9 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 ## To create the Extended Events session  
  Use Query Editor to create the Extended Events session, and to write the output to a file target. The following steps describe a single query, with explanations to show you how to build the query. For the full query example, see the "Example" section of this topic.  
 
-1.  Add statements to create the event session, replacing s*ession_name* with the name that you want to use for the Extended Events session.  
+1.  Add statements to create the event session, replacing *session_name* with the name that you want to use for the Extended Events session.  
 
-    ```  
+    ```sql
     IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
        DROP EVENT SESSION [Session_Name] ON SERVER;  
     CREATE EVENT SESSION [Session_Name]  
@@ -127,7 +127,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
      To convert this to the Extended Events equivalent, the sqlserver.sp_statement_starting and the sqlserver.sp_statement_completed events are added, with a list of actions. Predicate statements are included as WHERE clauses.  
 
-    ```  
+    ```sql
     ADD EVENT sqlserver.sp_statement_starting  
        (ACTION  
           (  
@@ -153,9 +153,9 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
        )  
     ```  
 
-3.  Add the asynchronous file target, replacing the file paths with the location where you want to save the ouput. When specifying the file target, you must include a log file and metadata file path file.  
+3.  Add the asynchronous file target, replacing the file paths with the location where you want to save the output. When specifying the file target, you must include a log file and metadata file path file.  
 
-    ```  
+    ```sql
     ADD TARGET package0.asynchronous_file_target(  
        SET filename='c:\temp\ExtendedEventsStoredProcs.xel', metadatafile='c:\temp\ExtendedEventsStoredProcs.xem');  
     ```  
@@ -164,7 +164,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
 1.  You can use the sys.fn_xe_file_target_read_file function to view the output. To do this, run the following query, replacing the file paths with the paths that you specified:  
 
-    ```  
+    ```sql
     SELECT *, CAST(event_data as XML) AS 'event_data_XML'  
     FROM sys.fn_xe_file_target_read_file('c:\temp\ExtendedEventsStoredProcs*.xel', 'c:\temp\ExtendedEventsStoredProcs*.xem', NULL, NULL);  
   
@@ -175,7 +175,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
      For more information about the sys.fn_xe_file_target_read_file function, see [sys.fn_xe_file_target_read_file &#40;Transact-SQL&#41;](../../relational-databases/system-functions/sys-fn-xe-file-target-read-file-transact-sql.md).  
 
-    ```  
+    ```sql
     IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
        DROP EVENT SESSION [session_name] ON SERVER;  
     CREATE EVENT SESSION [session_name]  
@@ -211,7 +211,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
 ## Example  
 
-```  
+```sql
 IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='session_name')  
    DROP EVENT SESSION [session_name] ON SERVER;  
 CREATE EVENT SESSION [session_name]  

docs/relational-databases/performance/adaptive-query-processing.md

@@ -269,7 +269,7 @@ Interleaved execution changes the unidirectional boundary between the optimizati
 
 MSTVFs have a fixed cardinality guess of 100 starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], and 1 for earlier [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] versions. Interleaved execution helps workload performance issues that are due to these fixed cardinality estimates associated with MSTVFs. For more information on MSTVFs, see [Create User-defined Functions (Database Engine)](../../relational-databases/user-defined-functions/create-user-defined-functions-database-engine.md#TVF).
 
-The following image depicts a [Live Query Statistics](../../relational-databases/performance/live-query-statistics.md) ouput, a subset of an overall execution plan that shows the impact of fixed cardinality estimates from MSTVFs. You can see the actual row flow vs. estimated rows. There are three noteworthy areas of the plan (flow is from right to left):
+The following image depicts a [Live Query Statistics](../../relational-databases/performance/live-query-statistics.md) output, a subset of an overall execution plan that shows the impact of fixed cardinality estimates from MSTVFs. You can see the actual row flow vs. estimated rows. There are three noteworthy areas of the plan (flow is from right to left):
 1. The MSTVF Table Scan has a fixed estimate of 100 rows. For this example, however, there are 527,597 rows flowing through this MSTVF Table Scan, as seen in Live Query Statistics via the *527597 of 100* actual of estimated – so the fixed estimate is significantly skewed.
 1. For the Nested Loops operation, only 100 rows are assumed to be returned by the outer side of the join. Given the high number of rows actually being returned by the MSTVF, you are likely better off with a different join algorithm altogether.
 1. For the Hash Match operation, notice the small warning symbol, which in this case is indicating a spill to disk.

docs/relational-databases/system-stored-procedures/sp-addextendedproperty-transact-sql.md

@@ -66,8 +66,7 @@ sp_addextendedproperty
  Is the name of the level 0 object type specified. *level0_object_name* is **sysname** with a default of NULL.  
 
  [ @level1type= ] { '*level1_object_type*' }  
- Is the type of level 1 object. *level1_object_type* is **varchar(128)**, with a default of NULL. Valid inputs are AGGREGATE, DEFAULT, FUNCTION, LOGICAL FILE NAME, PROCEDURE, QUEUE, RULE, SYNONYM, TABLE, TABLE_TYPE, TYPE, VIEW, XML SCHEMA COLLECTION, and NULL.  
-  
+ Is the type of level 1 object. *level1_object_type* is **varchar(128)**, with a default of NULL. Valid inputs are AGGREGATE, DEFAULT, FUNCTION, LOGICAL FILE NAME, PROCEDURE, QUEUE, RULE, SEQUENCE, SYNONYM, TABLE, TABLE_TYPE, TYPE, VIEW, XML SCHEMA COLLECTION, and NULL.    
  [ @level1name= ] { '*level1_object_name*' }  
  Is the name of the level 1 object type specified. *level1_object_name* is **sysname**, with a default of NULL.  
 

docs/t-sql/functions/pack-sent-transact-sql.md

@@ -15,7 +15,7 @@ dev_langs:
 helpviewer_keywords: 
   - "number of output packets written"
   - "@@PACK_SENT function"
-  - "packets [SQL Server], ouput"
+  - "packets [SQL Server], output"
   - "networking [SQL Server], output packets"
   - "connections [SQL Server], packets"
   - "output packets written to network [SQL Server]"
@@ -33,7 +33,7 @@ manager: craigg
 
 ## Syntax  
 
-```  
+```sql
 @@PACK_SENT  
 ```  
 
@@ -46,7 +46,7 @@ manager: craigg
 ## Examples  
  The following example shows the usage of `@@PACK_SENT`.  
 
-```  
+```sql
 SELECT @@PACK_SENT AS 'Pack Sent';  
 ```  
 

docs/t-sql/statements/create-database-transact-sql.md

@@ -1073,10 +1073,7 @@ The name of the database that is to be copied.
 Databases in [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] have several default settings that are set when the database is created. For more information about these default settings, see the list of values in [DATABASEPROPERTYEX](../../t-sql/functions/databasepropertyex-transact-sql.md).  
 
 MAXSIZE provides the ability to limit the size of the database. If the size of the database reaches its MAXSIZE, you receive error code 40544. When this occurs, you cannot insert or update data, or create new objects (such as tables, stored procedures, views, and functions). However, you can still read and delete data, truncate tables, drop tables and indexes, and rebuild indexes. You can then update MAXSIZE to a value larger than your current database size or delete some data to free storage space. There may be as much as a fifteen-minute delay before you can insert new data.  
-  
-> [!IMPORTANT]  
->  The `CREATE DATABASE` statement must be the only statement in a [!INCLUDE[tsql](../../includes/tsql-md.md)] batch. 
-  
+   
 To change the size, edition, or service objective values later, use [ALTER DATABASE (Azure SQL Database)](../../t-sql/statements/alter-database-transact-sql.md?&tabs=sqldbls).  
 
 The CATALOG_COLLATION argument is only available during database creation.