Merge pull request #32637 from MicrosoftDocs/FromPublicRepo

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

Author: rwestMSFT

docs/database-engine/availability-groups/windows/contained-availability-groups-overview.md

@@ -53,6 +53,9 @@ The system databases in a newly created contained AG aren't copies from the inst
 
 If you create local users or configurations in your instance, they don't automatically appear when you create your contained system databases, and they aren't visible when you connect to the contained AG. Once the user database has been joined to a contained AG, it will immediately become inaccessible to these users. You need to manually re-create them in the contained system databases within the context of the contained AG, by connecting directly to the database or by using the listener endpoint. The exception to this is that all of the logins in the sysadmin role in the parent instance are copied into the new AG specific `master` database.
 
+> [!NOTE]  
+> Because the `master` database is separate for each contained availability group, server-scope activities performed in the context of the contained AG are only persisted in the contained system database. This includes auditing. If you audit server level activity with SQL Server Auditing, you must create the same server audits within each contained AG.
+
 #### Restore a contained system database
 
 You can restore a contained system database using one of two different ways.

docs/relational-databases/security/dynamic-data-masking.md

@@ -63,7 +63,7 @@ You don't need any special permission to create a table with a dynamic data mask
 Adding, replacing, or removing the mask of a column, requires the **ALTER ANY MASK** permission and **ALTER** permission on the table. It's appropriate to grant **ALTER ANY MASK** to a security officer.
 
 > [!NOTE]  
-> The UNMASK permission does not influence metadata visibility: granting UNMASK alone doesn't disclose any metadata. UNMASK will always need to be accompanied by a SELECT permission to have any effect. Example: granting UNMASK on database scope and granting SELECT on an individual Table will have the result that the user can only see the metadata of the individual table from which he can select, not any others. Also see [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md).
+> The UNMASK permission does not influence metadata visibility: granting UNMASK alone doesn't disclose any metadata. UNMASK will always need to be accompanied by a SELECT permission to have any effect. Example: granting UNMASK on database scope and granting SELECT on an individual Table will have the result that the user can only see the metadata of the individual table from which they can select, not any others. Also see [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md).
 
 ## Best practices and common use cases
 

docs/t-sql/statements/alter-database-scoped-configuration-transact-sql.md

@@ -453,7 +453,7 @@ Sets [!INCLUDE [tsql](../../includes/tsql-md.md)] and query processing behaviors
 
 #### EXEC_QUERY_STATS_FOR_SCALAR_FUNCTIONS = { ON | OFF }
 
-**Applies to:** [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [ssazuremi](../../includes/ssazuremi-md.md)]
+**Applies to:** [!INCLUDE [sql-server-2022](../../includes/sssql22-md.md)] and later versions, [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], and [!INCLUDE [ssazuremi](../../includes/ssazuremi-md.md)]
 
 Allows you to control whether execution statistics for scalar user-defined functions (UDF) appear in the [sys.dm_exec_function_stats](../../relational-databases/system-dynamic-management-views/sys-dm-exec-function-stats-transact-sql.md) system view. For some intensive workloads that are scalar UDF-heavy, collecting function execution statistics might cause a noticeable performance overhead. This can be avoided by setting the `EXEC_QUERY_STATS_FOR_SCALAR_FUNCTIONS` database-scoped configuration to `OFF`.  The default is **ON**. 
 

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

@@ -1367,6 +1367,8 @@ CREATE DATABASE database_name [ COLLATE collation_name ]
 ```
 > [!IMPORTANT]
 > To add files or set containment for a database in a managed instance, use the [ALTER DATABASE](alter-database-transact-sql.md?tabs=sqldbmi) statement.
+>
+> For SQL managed instances, the initial MAXSIZE is implicitly set to the current disk size, and it doesn't change automatically when you extend the disk size from the Azure portal. After extending the disk, you should also extend MAXSIZE with [ALTER DATABASE](alter-database-transact-sql.md?tabs=sqldbmi) to avoid database file full errors.
 
 ## Arguments
 

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

@@ -59,7 +59,6 @@ Creates a new table in the database.
 > For reference to [!INCLUDE [fabricdw](../../includes/fabric-dw.md)] in [!INCLUDE [fabric](../../includes/fabric.md)], visit [CREATE TABLE (Fabric Data Warehouse)](create-table-azure-sql-data-warehouse.md?view=fabric&preserve-view=true).
 > For reference to [!INCLUDE[ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] and [!INCLUDE[ssPDW](../../includes/sspdw-md.md)], visit [CREATE TABLE (Azure Synapse Analytics)](create-table-azure-sql-data-warehouse.md?view=azure-sqldw-latest&preserve-view=true).
 
-
 :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
 ## Syntax options
@@ -109,7 +108,7 @@ column_name <data_type>
     [ SPARSE ]
     [ MASKED WITH ( FUNCTION = 'mask_function' ) ]
     [ [ CONSTRAINT constraint_name ] DEFAULT constant_expression ]
-    [ IDENTITY [ ( seed , increment ) ]
+    [ IDENTITY [ ( seed , increment ) ] ]
     [ NOT FOR REPLICATION ]
     [ GENERATED ALWAYS AS { ROW | TRANSACTION_ID | SEQUENCE_NUMBER } { START | END } [ HIDDEN ] ]
     [ [ CONSTRAINT constraint_name ] {NULL | NOT NULL} ]
@@ -253,7 +252,7 @@ column_set_name XML COLUMN_SET FOR ALL_SPARSE_COLUMNS
           { (
              FILTER_COLUMN = column_name,
              RETENTION_PERIOD = { INFINITE | number { DAY | DAYS | WEEK | WEEKS
-                              | MONTH | MONTHS | YEAR | YEARS }
+                              | MONTH | MONTHS | YEAR | YEARS } }
         ) }
     ]
     [ LEDGER = ON [ ( <ledger_option> [ ,... n ] ) ]