Merge pull request #18224 from MicrosoftDocs/FromPublicRepo

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

Author: huypub

docs/azure-data-studio/download-azure-data-studio.md

@@ -145,6 +145,7 @@ Azure Data Studio runs on Windows, macOS, and Linux and is supported on the foll
 - macOS 10.14 Mojave
 - macOS 10.13 High Sierra
 - macOS 10.12 Sierra
+- macOS 11.1  Big Sur
 
 ### Linux
 

docs/odbc/reference/syntax/sqlcolattribute-function.md

@@ -71,7 +71,7 @@ SQLRETURN SQLColAttribute (
   
 -   If *CharacterAttributePtr* is a pointer to a binary buffer, the application places the result of the SQL_LEN_BINARY_ATTR(*length*) macro in *BufferLength*. This places a negative value in *BufferLength*.  
   
--   If *CharacterAttributePtr* is a pointer to a fixed-length data type, *BufferLength* must be one of the following: SQL_IS_INTEGER, SQL_IS_UNINTEGER, SQL_SMALLINT, or SQLUSMALLINT.  
+-   If *CharacterAttributePtr* is a pointer to a fixed-length data type, *BufferLength* must be one of the following: SQL_IS_INTEGER, SQL_IS_UINTEGER, SQL_IS_SMALLINT, or SQL_IS_USMALLINT.  
   
  *StringLengthPtr*  
  [Output] Pointer to a buffer in which to return the total number of bytes (excluding the null-termination byte for character data) available to return in **CharacterAttributePtr*.  

docs/relational-databases/system-catalog-views/sys-server-file-audits-transact-sql.md

@@ -34,7 +34,7 @@ ms.author: wiassaf
 |create_date|**datetime**|UTC date when the file audit was created.|  
 |modify_date|**datatime**|UTC date when the file audit was last modified.|  
 |principal_id|**int**|ID of the owner of the audit as registered on the server.|  
-|type|**char(2)**|Audit type:<br /><br /> 0 = NT Security event log<br /><br /> 1 = NT Application event log<br /><br /> 2 = File on file system|  
+|type|**char(2)**|Audit type:<br /><br /> SL = NT Security event log<br /><br /> AL = NT Application event log<br /><br /> FL = File on file system|  
 |type_desc|**nvarchar(60)**|Audit type description.|  
 |on_failure|**tinyint**|On Failure condition:<br /><br /> 0 = Continue<br /><br /> 1 = Shut down server instance<br /><br /> 2 = Fail operation|  
 |on_failure_desc|**nvarchar(60)**|On Failure to write an action entry:<br /><br /> CONTINUE<br /><br /> SHUTDOWN SERVER INSTANCE<br /><br /> FAIL OPERATION|  

docs/relational-databases/system-dynamic-management-views/sys-dm-io-virtual-file-stats-transact-sql.md

@@ -25,7 +25,7 @@ monikerRange: "=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sq
 # sys.dm_io_virtual_file_stats (Transact-SQL)
 [!INCLUDE [sql-asdb-asdbmi-asa-pdw](../../includes/applies-to-version/sql-asdb-asdbmi-asa.md)]
 
-  Returns I/O statistics for data and log files. This dynamic management view replaces the [fn_virtualfilestats](../../relational-databases/system-functions/sys-fn-virtualfilestats-transact-sql.md) function.  
+  Returns I/O statistics for data and log files. This dynamic management function replaces the [fn_virtualfilestats](../../relational-databases/system-functions/sys-fn-virtualfilestats-transact-sql.md) function.  
 
 > [!NOTE]  
 >  To call this from [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)], use the name **sys.dm_pdw_nodes_io_virtual_file_stats**. 

docs/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql.md

@@ -61,7 +61,7 @@ The file to be shrunk's logical name.
 The file to be shrunk's identification (ID) number. To get a file ID, use the [FILE_IDEX](../../t-sql/functions/file-idex-transact-sql.md) system function or query the [sys.database_files](../../relational-databases/system-catalog-views/sys-database-files-transact-sql.md) catalog view in the current database.
 
 *target_size*  
-An integer - the file's new megabyte size. If not specified, DBCC SHRINKFILE reduces to the file creation size.
+An integer - the file's new megabyte size. If not specified or 0, DBCC SHRINKFILE reduces to the file creation size.
 
 > [!NOTE]  
 >  You can reduce an empty file's default size using DBCC SHRINKFILE *target_size*. For example, if you create a 5-MB file and then shrink the file to 3 MB while the file is still empty, the default file size is set to 3 MB. This applies only to empty files that have never contained data.  

docs/t-sql/functions/logical-functions-iif-transact-sql.md

@@ -29,7 +29,7 @@ ms.author: chadam
 ## Syntax  
 
 ```syntaxsql
-IIF ( boolean_expression, true_value, false_value )  
+IIF( boolean_expression, true_value, false_value )
 ```  
 
 [!INCLUDE[sql-server-tsql-previous-offline-documentation](../../includes/sql-server-tsql-previous-offline-documentation.md)]
@@ -38,7 +38,7 @@ IIF ( boolean_expression, true_value, false_value )
  *boolean_expression*  
  A valid Boolean expression.  
 
- If this argument is not a Boolean expression, then a syntax error is raised.  
+ If this argument is not a Boolean expression then a syntax error is raised.  
 
  *true_value*  
  Value to return if *boolean_expression* evaluates to true.  
@@ -59,8 +59,8 @@ IIF ( boolean_expression, true_value, false_value )
 ### A. Simple IIF example  
 
 ```sql  
-DECLARE @a INT = 45, @b INT = 40;  
-SELECT IIF ( @a > @b, 'TRUE', 'FALSE' ) AS Result;  
+DECLARE @a INT = 45, @b INT = 40;
+SELECT [Result] = IIF( @a > @b, 'TRUE', 'FALSE' );
 ```  
 
  [!INCLUDE[ssResult](../../includes/ssresult-md.md)]  
@@ -69,14 +69,12 @@ SELECT IIF ( @a > @b, 'TRUE', 'FALSE' ) AS Result;
 Result  
 --------  
 TRUE  
-  
-(1 row(s) affected)  
 ```  
 
 ### B. IIF with NULL constants  
 
 ```sql 
-SELECT IIF ( 45 > 30, NULL, NULL ) AS Result;  
+SELECT [Result] = IIF( 45 > 30, NULL, NULL );
 ```  
 
  The result of this statement is an error.  
@@ -85,7 +83,7 @@ SELECT IIF ( 45 > 30, NULL, NULL ) AS Result;
 
 ```sql  
 DECLARE @P INT = NULL, @S INT = NULL;  
-SELECT IIF ( 45 > 30, @p, @s ) AS Result;  
+SELECT [Result] = IIF( 45 > 30, @P, @S );
 ```  
 
  [!INCLUDE[ssResult](../../includes/ssresult-md.md)]  
@@ -94,8 +92,6 @@ SELECT IIF ( 45 > 30, @p, @s ) AS Result;
 Result  
 --------  
 NULL  
-  
-(1 row(s) affected)  
 ```  
 
 ## See Also  

docs/t-sql/statements/set-textsize-transact-sql.md

@@ -29,7 +29,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 # SET TEXTSIZE (Transact-SQL)
 [!INCLUDE [sql-asdb-asdbmi-asa-pdw](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-  Specifies the size of **varchar(max)**, **nvarchar(max)**, **varbinary(max)**, **text**, **ntext**, and **image** data returned by a SELECT statement.  
+  Specifies the size, in bytes, of **varchar(max)**, **nvarchar(max)**, **varbinary(max)**, **text**, **ntext**, and **image** data returned to the client by a SELECT statement.  
 
 > [!IMPORTANT]
 >  **ntext**, **text**, and **image** data types will be removed in a future version of [!INCLUDE[msCoName](../../includes/msconame-md.md)][!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use **nvarchar(max)**, **varchar(max)**, and **varbinary(max)** instead.  

docs/tools/sqlcmd-utility.md

@@ -914,14 +914,22 @@ Use the following practices to help maximize security and efficiency.
 
 - Use integrated security.  
 
-- Use **-X** in automated environments.  
+- Use **-X[1]** in automated environments.
 
 - Secure input and output files by using appropriate NTFS file system permissions.
 
 - To increase performance, do as much in one **sqlcmd** session as you can, instead of in a series of sessions.
 
 - Set time-out values for batch or query execution higher than you expect it will take to execute the batch or query.
 
+Use the following practices to help maximize correctness:
+
+- Use **-V16** to log any [severity 16 level messages](../relational-databases/errors-events/database-engine-error-severities.md#levels-of-severity).  Severity 16 messages indicates general errors that can be corrected by the user.
+
+- Check the exit code and DOS ERRORLEVEL variable after the process has exited.  **sqlcmd** will return 0 normally, otherwise it will set the ERRORLEVEL as configured by **-V**.  In other words, ERRORLEVEL shouldn't be expected to be the same value as the Error Number reported from SQL Server. The Error Number is a SQL Server-specific value corresponding to the system function [**@@ERROR**](../t-sql/functions/error-transact-sql.md).  ERRORLEVEL is a SQLCMD-specific value to indicate why it (i.e. SQLCMD) terminated, and it's value is influenced by specifying **-b** command line argument.
+
+Using **-V16** in combination with checking the exit code and DOS ERRORLEVEL can help catch errors in automated environments, particularly quality gates before a production release.
+
 ## Next steps
 
 - [Start the sqlcmd Utility](~/relational-databases/scripting/sqlcmd-start-the-utility.md)