For a database with memory optimized tables in sql server 2016 is row versioning 'ON' by default? sys.databases shows isolation level of read committed. If in a stored proc we put "with (snapshot)" hint how can we know if it actually used row versioning. We have a stored procedure that just does a select. Would think if row versioning is not being done at insert/update/delete then putting "with (snapshot" hint in just the select would do nothing. If we alter database and set isolation as sapshot at database level, will it make update/inserts a little slower as it will start making multiple copies of the rows? Will we still have to put hint "with (snapshot)" with the selects as is done with "with (nolock)" for regular disk tables.
