Merge branch 'main' into release-2017-cu30

Author: v-alje

azure-sql/managed-instance/resource-limits.md

@@ -56,13 +56,20 @@ Support for the premium-series hardware (public preview) is currently available
 | Region | **Premium-series** | **Memory optimized premium-series** | 
 |:--- |:--- |:--- |
 | Australia Central | Yes | | 
-| Australia East | Yes | | 
-| Canada Central | Yes | | 
+| Australia East | Yes | Yes | 
+| Australia Southeast | Yes | Yes | 
+| Brazil South | Yes | Yes |
+| Canada Central | Yes | Yes | 
 | Canada East | Yes | | 
 | Central US | Yes | Yes | 
+| East Asia | Yes | | 
 | East US | Yes | Yes | 
+| East US 2 | Yes | Yes | 
+| France Central | Yes | Yes | 
+| France South | Yes | | 
 | Germany West Central | Yes | Yes | 
-| Japan East | Yes | | 
+| India Central | Yes | Yes | 
+| Japan East | Yes | Yes | 
 | Japan West | Yes | | 
 | Korea Central | Yes | | 
 | North Central US | Yes | Yes | 
@@ -71,15 +78,15 @@ Support for the premium-series hardware (public preview) is currently available
 | South Africa West | Yes | | 
 | South Central US | Yes | Yes | 
 | Southeast Asia | Yes |  | 
-| Sweden Central | | Yes | 
+| Sweden Central | Yes | Yes | 
 | Switzerland North | Yes | | 
 | Switzerland West | Yes | | 
 | UAE North | Yes | | 
 | UK South | Yes | Yes | 
 | UK West | Yes | | 
 | West Central US | Yes | | 
 | West Europe | Yes | Yes | 
-| West US | Yes | |  
+| West US | Yes | Yes |  
 | West US 2 | Yes | Yes | 
 | West US 3 | Yes | Yes | 
 

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -487,7 +487,7 @@ Service broker is enabled by default and cannot be disabled. The following ALTER
   - `scan for startup procs`
 - The following [sp_configure](/sql/relational-databases/system-stored-procedures/sp-configure-transact-sql) options are ignored and have no effect: 
   - `Ole Automation Procedures`
-- `sp_execute_external_scripts` isn't supported. See [sp_execute_external_scripts](/sql/relational-databases/system-stored-procedures/sp-execute-external-script-transact-sql#examples).
+- `sp_execute_external_scripts` is only supported for [Machine Learning Services for SQL MI](machine-learning-services-overview.md), otherwise **sp_execute_external_scripts** is not supported for SQL Managed Instance. See [sp_execute_external_scripts](/sql/relational-databases/system-stored-procedures/sp-execute-external-script-transact-sql#examples).
 - `xp_cmdshell` isn't supported. See [xp_cmdshell](/sql/relational-databases/system-stored-procedures/xp-cmdshell-transact-sql).
 - `Extended stored procedures` aren't supported, and this includes `sp_addextendedproc` and `sp_dropextendedproc`. This functionality won't be supported because it's on a deprecation path for SQL Server. For more information, see [Extended Stored Procedures](/sql/relational-databases/extended-stored-procedures-programming/database-engine-extended-stored-procedures-programming).
 - `sp_attach_db`, `sp_attach_single_file_db`, and `sp_detach_db` aren't supported. See [sp_attach_db](/sql/relational-databases/system-stored-procedures/sp-attach-db-transact-sql), [sp_attach_single_file_db](/sql/relational-databases/system-stored-procedures/sp-attach-single-file-db-transact-sql), and [sp_detach_db](/sql/relational-databases/system-stored-procedures/sp-detach-db-transact-sql).

docs/relational-databases/accelerated-database-recovery-management.md

@@ -1,7 +1,7 @@
 ---
 description: "Best practices for managing and configuring accelerated database recovery (ADR)."
 title: "Manage accelerated database recovery | Microsoft Docs"
-ms.date: 06/10/2022
+ms.date: 07/12/2022
 ms.prod: sql
 ms.prod_service: backup-restore
 ms.technology: backup-restore
@@ -27,7 +27,7 @@ This article contains information on best practices for managing and configuring
 
 Many customers find accelerated database recovery (ADR) a valuable technology to improve recovery time. An accumulation of the factors below should be considered before deciding which databases should use ADR, evaluate the factors below and if the accumulation of factors weighs in favor or against using ADR. 
 
-- ADR is recommended for workloads with long running transactions. 
+- ADR is recommended for workloads with long running transactions that cannot be avoided. For example, in cases where long-running transactions are at risk of being rolled back, ADR can help.
 
 - ADR is recommended for workloads that have seen cases where active transactions are causing the transaction log to grow significantly.  
 
@@ -59,7 +59,7 @@ This section contains guidance and recommendations for ADR.
 
 - Ensure there is sufficient space on the database to account for PVS usage. If the database does not have enough room for the PVS to grow, ADR will fail to generate versions. ADR saves space in the version store compared to `tempdb` version store. 
 
-- Avoid long-running transactions in the database. Though one objective of ADR is to speed up database recovery due to redo long active transactions, long-running transactions can delay version cleanup and increase the size of the PVS.
+- Avoid multiple long-running transactions in the database. Though one objective of ADR is to speed up database recovery due to redo, multiple long-running transactions can delay version cleanup and increase the size of the PVS.
 
 - Avoid large transactions with data definition changes or DDL operations. ADR uses a SLOG (system log stream) mechanism to track DDL operations used in recovery. The SLOG is only used while the transaction active. SLOG is checkpointed, so avoiding large transactions that use SLOG can help overall performance. These scenarios can cause the SLOG to take up more space:
 
@@ -79,8 +79,7 @@ This section contains guidance and recommendations for ADR.
 ADR is off by default in [!INCLUDE[sql-server-2019](../includes/sssql19-md.md)], and can be controlled using DDL syntax:
 
 ```syntaxsql
-ALTER DATABASE [DB] SET ACCELERATED_DATABASE_RECOVERY = {ON | OFF}
-[(PERSISTENT_VERSION_STORE_FILEGROUP = { filegroup name }) ];
+ALTER DATABASE [DB] SET ACCELERATED_DATABASE_RECOVERY = {ON | OFF};
 ```
 
 Use this syntax to control whether the feature is on or off, and designate a specific filegroup for the *persistent version store* (PVS) data. If no filegroup is specified, the PVS will be stored in the PRIMARY filegroup. 
@@ -89,25 +88,42 @@ An exclusive lock is necessary on the database to change this state.  That means
 
 ## Managing the persistent version store filegroup
 
-The ADR feature is based on having changes versioned, with different versions of a data element kept in the PVS.
-There are considerations to locating where the PVS is located and in how to manage the size of the data in the PVS.
+The ADR feature is based on having changes versioned, with different versions of a data element kept in the PVS. There are considerations to locating where the PVS is located and in how to manage the size of the data in the PVS.
 
 ### To enable ADR without specifying a filegroup
 
+This operation requires exclusive access to the database.
+
 ```sql
 ALTER DATABASE [MyDatabase] SET ACCELERATED_DATABASE_RECOVERY = ON;
 GO
 ```
 
 In this case, when the PVS filegroup is not specified, the `PRIMARY` filegroup holds the PVS data.
 
-### To enable ADR and specify that the PVS should be stored in the [VersionStoreFG] filegroup
+### To enable ADR and specify that the PVS should be stored in a filegroup
+
+You can configure ADR to use another filegroup, aside from the default `PRIMARY` filegroup, to hold PVS data.
+
+Before enabling ADR in a filegroup besides `PRIMARY`, you must create the filegroup and data file. 
+
+Create the `VersionStoreFG` filegroup and create a new data file in the filegroup. For example:
+
+```sql
+ALTER DATABASE [MyDatabase] ADD FILEGROUP [VersionStoreFG];
+GO
+ALTER DATABASE [MyDatabase] ADD FILE ( NAME = N'VersionStoreFG'
+, FILENAME = N'E:\DATA\VersionStore.ndf'
+, SIZE = 8192KB , FILEGROWTH = 65536KB )
+TO FILEGROUP [VersionStoreFG];
+GO
+```
 
-Before running this script, create the filegroup.
+Only after the filegroup and a secondary data file have been created, enable ADR and specify that the PVS should be stored in a specific filegroup. This operation requires exclusive access to the database. 
 
 ```sql
 ALTER DATABASE [MyDatabase] SET ACCELERATED_DATABASE_RECOVERY = ON
-(PERSISTENT_VERSION_STORE_FILEGROUP = [VersionStoreFG])
+(PERSISTENT_VERSION_STORE_FILEGROUP = [VersionStoreFG]);
 ```
 
 ### To disable the ADR feature
@@ -132,7 +148,7 @@ Changing the location of the PVS is a three-step process.
    GO
    ```
 
-2. Wait until all of the versions stored in the PVS can be freed
+2. Wait until all of the versions stored in the PVS can be freed.
 
    In order to be able to turn on ADR with a new location for the persistent version store, you must first make sure that all of the version information has been purged from the previous PVS location. In order to force that cleanup to happen, run the command:
 
@@ -147,7 +163,7 @@ Changing the location of the PVS is a three-step process.
    FROM sys.dm_tran_persistent_version_store_stats where database_id = [MyDatabaseID];
    ```
 
-   When the value of `persistent_version_store_size_kb` is 0, you can re-enable the ADR feature, configuring the PVS to be located in the new filegroup.
+   When the value of `persistent_version_store_size_kb` is `0`, you can re-enable the ADR feature, configuring the PVS to be located in the new filegroup.
 
 3. Turn on ADR, specifying the new location for the PVS:
 

docs/relational-databases/accelerated-database-recovery-troubleshoot.md

@@ -1,7 +1,7 @@
 ---
 description: "Troubleshoot accelerated database recovery"
 title: "Troubleshoot accelerated database recovery"
-ms.date: "06/10/2022"
+ms.date: 07/12/2022
 ms.prod: sql
 ms.prod_service: backup-restore
 ms.technology: backup-restore
@@ -57,7 +57,7 @@ WHERE pvss.database_id = DB_ID();
 
 1. Check `pvs_pct_of_database_size` size, note any difference from the typical, compared to baselines during other periods of application activity. PVS is considered large if it's significantly larger than baseline or if it is close to 50% of the size of the database. Use the following steps as a troubleshooting aid for a PVS that is large.
 
-2. Active transactions prevent cleaning up the PVS. Retrieve `oldest_active_transaction_id` and check whether this transaction has been active for a long time by querying `sys.dm_tran_database_transactions` based on the transaction ID. Check for long-running, active transactions with a query like the below sample, which declares variables to set thresholds for duration or log amount:
+2. Active, long-running transactions in any database where ADR is enabled can prevent cleanup of the PVS. Retrieve `oldest_active_transaction_id` and check whether this transaction has been active for a long time by querying `sys.dm_tran_database_transactions` based on the transaction ID. Check for long-running, active transactions with a query like the below sample, which declares variables to set thresholds for duration or log amount:
 
     ```sql
     DECLARE @longTxThreshold int = 1800; --number of seconds to use as a duration threshold for long-running transactions
@@ -108,7 +108,7 @@ WHERE pvss.database_id = DB_ID();
 
     To prevent delays to PVS cleanup:
 
-    1. Consider killing the long active transaction session that is delaying PVS cleanup, if possible. 
+    1. Consider killing the long active transaction session that is delaying PVS cleanup, if possible. Long-running transactions in any database where ADR is enabled may delay ADR PVS cleanup.
     1. Tune long-running queries to reduce query duration and locks required. For more information and guidance, see [Understand and resolve blocking in SQL Server](/troubleshoot/sql/performance/understand-resolve-blocking) or [Understand and resolve Azure SQL Database blocking problems](/azure/azure-sql/database/understand-resolve-blocking).
     1. Review the application to determine the nature of the problematic active snapshot scan. Consider a different isolation level, such as READ COMMITTED, instead of SNAPSHOT or READ COMMITTED SNAPSHOT for long-running queries that are delaying ADR PVS cleanup. This problem occurs more frequently with SNAPSHOT isolation level.
     1. This issue can occur in SQL Server, Azure SQL Managed Instance, and elastic pools of Azure SQL Database, but not in singleton Azure SQL databases. In Azure SQL Database elastic pools, consider moving databases out of the elastic pool that have long-running queries using READ COMMIT SNAPSHOT or SNAPSHOT isolation levels.

docs/relational-databases/databases/tempdb-database.md

@@ -18,7 +18,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 ---
 # tempdb database
 
-[!INCLUDE [SQL Server Azure SQL Database](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
 
 This article describes the `tempdb` system database, a global resource available to all users connected to an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], Azure SQL Database, or Azure SQL Managed Instance. 
 
@@ -203,7 +203,8 @@ Metadata contention in `tempdb` has historically been a bottleneck to scalabilit
 
 This feature effectively removes this bottleneck and unlocks a new level of scalability for tempdb-heavy workloads. In [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], the system tables involved in managing temporary table metadata can be moved into latch-free, non-durable, memory-optimized tables.
 
-Currently the memory-optimized tempdb metadata feature is not available in Azure SQL Database or Azure SQL Managed Instance.
+> [!NOTE]
+> Currently the memory-optimized tempdb metadata feature is not available in Azure SQL Database or Azure SQL Managed Instance.
 
 Watch this seven-minute video for an overview of how and when to use memory-optimized tempdb metadata:
 

docs/relational-databases/event-classes/audit-login-gdr-event-class.md

@@ -15,7 +15,7 @@ ms.author: wiassaf
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Audit Login GDR Event Class
-[!INCLUDE [SQL Server - ASDB](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
   The **Audit Login GDR** event class occurs whenever a [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows login right is added or removed. This event class is for the **sp_grantlogin**, **sp_revokelogin**, and **sp_denylogin** stored procedures.  
 
  This event class may be removed in a future version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. It is recommended that you use the **Audit Server Principal Management** event class instead.  

docs/relational-databases/event-classes/audit-logout-event-class.md

@@ -15,7 +15,7 @@ ms.author: wiassaf
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Audit Logout Event Class
-[!INCLUDE [SQL Server - ASDB](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
   The **Audit Logout** event class indicates that a user has logged out of (logged off) [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Events in this class are fired by new connections or by connections that are reused from a connection pool.  
 
 ## Audit Logout Event Class Data Columns  

docs/relational-databases/event-classes/audit-object-derived-permission-event-class.md

@@ -15,7 +15,7 @@ ms.author: wiassaf
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Audit Object Derived Permission Event Class
-[!INCLUDE [SQL Server - ASDB](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
   The **Audit Object Derived Permission** event class records when a CREATE, ALTER, or DROP command is issued for a specified object. This event only occurs if the object does not have permissions or owners directly associated with it.  
 
  This event class may be removed in a future version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. It is recommended that you use the **Audit Schema Object Management** event class instead.  

docs/relational-databases/event-classes/audit-schema-object-access-event-class.md

@@ -15,7 +15,7 @@ ms.author: wiassaf
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Audit Schema Object Access Event Class
-[!INCLUDE [SQL Server - ASDB](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
   The **Audit Schema Object Access** event class occurs when an object permission (such as SELECT) is used.  
 
 ## Audit Schema Object Access Event Class Data Columns  

docs/relational-databases/event-classes/audit-schema-object-gdr-event-class.md

@@ -15,7 +15,7 @@ ms.author: wiassaf
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Audit Schema Object GDR Event Class
-[!INCLUDE [SQL Server - ASDB](../../includes/applies-to-version/sql-asdb.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
   The **Audit Schema Object GDR** event class occurs whenever a GRANT, REVOKE, or DENY is issued for a schema object permission by any user in [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
 
 ## Audit Schema Object GDR Event Class Data Columns