Refactor content

Author: dimitri-furman

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 
@@ -114,6 +114,16 @@ With elastic pools, the In-Memory OLTP storage is shared across all databases in
 - Configure a `Max eDTU` or `Max vCore` for databases that is lower than the eDTU or vCore count for the pool as a whole. This maximum also caps the In-Memory OLTP storage utilization in any database in the pool proportionally.
 - Configure a `Min eDTU` or `Min vCore` that is greater than 0. This minimum guarantees that each database in the pool has the amount of available In-Memory OLTP storage that corresponds to the configured `Min eDTU` or `Min vCore`.
 
+#### Point-in-time restore for databases 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 to a point in time](recovery-using-backups.md#point-in-time-restore), 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, follow this procedure:
+
+1. Restore the database using the Business Critical or Premium service tier.
+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.
+
 ### <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.

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

@@ -90,10 +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. 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, follow this procedure:
->   1. Restore the database using the Business Critical or Premium service tier.
->   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.
+> - 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 [Point-in-time restore for databases with In-Memory OLTP objects](in-memory-oltp-overview.md#point-in-time-restore-for-databases-with-in-memory-oltp-objects).
 
 - **Database replacement**