Merge pull request #33481 from dimitri-furman/dfurman/hk-restore

Add restore with XTP details

Author: prmerger-automator[bot]

azure-sql/database/in-memory-oltp-overview.md

@@ -4,7 +4,7 @@ description: In-memory technologies greatly improve the performance of transacti
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma
-ms.date: 09/19/2024
+ms.date: 03/13/2025
 ms.service: azure-sql-database
 ms.subservice: performance
 ms.topic: concept-article 
@@ -116,7 +116,7 @@ With elastic pools, the In-Memory OLTP storage is shared across all databases in
 
 ### <a id="changing-service-tiers-of-databases-that-use-in-memory-oltp-technologies"></a> Change service tiers of databases that use In-Memory OLTP technologies
 
-In-Memory OLTP isn't supported in the General Purpose, Standard, and Basic service tiers of Azure SQL Database. Therefore, it isn't possible to scale a database that has any In-Memory OLTP objects to one of these tiers. If you want to scale a database to one of these service tiers, remove all memory-optimized tables and table types as well as all natively compiled T-SQL modules, or convert them to disk-based objects and regular T-SQL modules.
+In-Memory OLTP isn't supported in the General Purpose, Standard, and Basic service tiers of Azure SQL Database. Therefore, it isn't possible to scale or [restore](#restore-a-database-with-in-memory-oltp-objects) a database that has any In-Memory OLTP objects to one of these tiers. If you want to scale a database to one of these service tiers, remove all memory-optimized tables and table types as well as all natively compiled T-SQL modules, or convert them to disk-based objects and regular T-SQL modules.
 
 When you scale down a Business Critical or a Premium database, data in the memory-optimized tables must fit within the In-Memory OLTP storage that is available in the destination service objective of the database or elastic pool. If you try to scale down the database or elastic pool, or move a database into an elastic pool, and the destination service objective doesn't have enough available In-Memory OLTP storage, the operation fails.
 
@@ -138,6 +138,15 @@ SELECT * FROM sys.table_types WHERE is_memory_optimized = 1;
 SELECT * FROM sys.sql_modules WHERE uses_native_compilation = 1;
 ```
 
+### Restore a database with In-Memory OLTP objects
+
+If you created any [In-Memory OLTP](in-memory-oltp-overview.md#in-memory-oltp) objects in a database and want to [restore the database](recovery-using-backups.md), you must use the Business Critical or Premium service tiers for the restored database. This applies even if you deleted all In-Memory OLTP objects before the restore point-in-time.
+
+To make future automatic backups of the database restorable in other service tiers after all In-Memory OLTP objects are deleted, follow this procedure:
+
+1. Scale the database to the General Purpose, Standard, or Basic service tier.
+1. If required, scale the database back to the Business Critical or Premium service tier, or to the Hyperscale service tier.
+
 ## In-memory columnstore
 
 In-memory columnstore technology is enabling you to store and query a large amount of data in the tables. Columnstore technology uses column-based data storage format and batch query processing to achieve gain up to 10 times the query performance in OLAP workloads over traditional row-oriented storage. You can also achieve gains up to 10 times the data compression over the uncompressed data size.

azure-sql/database/recovery-using-backups.md

@@ -5,7 +5,7 @@ description: Learn about point-in-time restore, which enables you to roll back a
 author: dnethi
 ms.author: dinethi
 ms.reviewer: wiassaf, mathoma, danil
-ms.date: 02/03/2025
+ms.date: 03/13/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -52,12 +52,12 @@ Several factors affect the recovery time to restore a database through automated
 
 - The size of the database
 - The compute size of the database
-- The number of transaction logs involved
+- The size of the transaction log backups involved
 - The amount of activity that needs to be replayed to recover to the restore point
 - The network bandwidth if the restore is to a different region
 - The number of concurrent restore requests that are processed in the target region
 
-For a large or very active database, the restore might take several hours. A prolonged outage in a region might cause a high number of geo-restore requests for disaster recovery. When there are many requests, the recovery time for individual databases can increase. For information on recovery times, see [RTO and RPO](business-continuity-high-availability-disaster-recover-hadr-overview.md?view=azuresql-db&preserve-view=true#rto-and-rpo).
+For a large or very active database in the service tiers other than [Hyperscale](service-tier-hyperscale.md), the restore might take several hours. A prolonged outage in a region might cause a high number of geo-restore requests for disaster recovery. When there are many requests, the recovery time for individual databases can increase. For information on recovery times, see [RTO and RPO](business-continuity-high-availability-disaster-recover-hadr-overview.md?view=azuresql-db&preserve-view=true#rto-and-rpo).
 
 For a single subscription, you have the following limitations on the number of concurrent restore requests. These limitations apply to any combination of point-in-time restores, geo-restores, and restores from long-term retention backup.
 
@@ -90,6 +90,7 @@ You generally restore a database to an earlier point for recovery purposes. You
 > - You can't perform a point-in-time restore on a geo-secondary database. You can do so only on a primary database.
 > - The `BackupFrequency` parameter isn't supported for Hyperscale databases.  
 > - Database restore operations are resource-intensive and might require a service tier of S3 or greater for the restoring (target) database. Once restore completes, the database or elastic pool might be scaled down, if required.
+> - If you created any [In-Memory OLTP](in-memory-oltp-overview.md#in-memory-oltp) objects in a database in the Business Critical or Premium service tiers, then you must use the Business Critical or Premium service tiers for the restored database. For more information, see [Restore a database with In-Memory OLTP objects](in-memory-oltp-overview.md#restore-a-database-with-in-memory-oltp-objects).
 
 - **Database replacement**