Hi
Manish Agarwal •,
Welcome to Microsoft Q&A forum and thanks for using Azure services.
As I understand, you are getting memory quota error when inserting records in Azure SQL Database in memory OLTP and want to now considerations when choosing the same.
Hitting the In-Memory OLTP storage cap in your database results in INSERT, UPDATE, ALTER and CREATE operations failing with error cause the active transaction to abort.
To resolve this error, either:
- Delete data from the memory-optimized tables, potentially offloading the data to traditional, disk-based tables; or,
- Upgrade the service tier to one with enough in-memory storage for the data you need to keep in memory-optimized tables.
In rare cases, this error can be transient, meaning there is enough available In-Memory OLTP storage, and retrying the operation succeeds. We therefore recommend to both monitor the overall available In-Memory OLTP storage and to retry when first encountering error 41823 or 41840. For more information about retry logic, see Conflict Detection and Retry Logic with In-Memory OLTP.
In Memory OLTP details are illustrated here in official blogpost by Microsoft: In-Memory OLTP in Azure SQL Database
Hope this helps. If this answers your query, do click Accept Answer
and Mark Helpful
for the same. And, if you have any further query do let us know.
Thank you.