What is the best practice location for Memorize Optimization (OLTP) files? Best practices for log and mdf files is to split across drives (e.g. G:\SQL Data &amp; I:\SQL Logs).
What are the best practices for memory optimization files? Should they reside on their own drive? Can they reside on a Azure Temp drive (better IO performance but files will be lost on redeploy, tempdb can be hosted here)?
I am still unclear on the purpose of the Memory Optimized file set and what is actually stored there and the rate of IO.
I think we are talking about In Memory OLTP ?
The files are necessary for disaster recovery
Once added they can't be removed without dropping the database !!!
You need x4 the amount of memory as disk files - if the disk files fill up your database will go suspect.
A fast disk subsystem is recommended.
I would advise careful testing before you deploy to production.
https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/the-memory-optimized-filegroup?view=sql-server-ver15