Ned Otter announces a new tool for troubleshooting memory-optimized databases:
Instance level evaluates the following:
-
the version/edition of SQL server
-
SQL Server ‘max memory’ setting
-
memory clerks
-
XTP memory consumers, aggregated
-
XTP memory consumers, detailed
-
the value of the committed_target_kb column from sys.dm_os_sys_info
-
whether or not instance-level collection of execution statistics has been enabled for all natively compiled stored procedures (because this can kill their performance….)
-
when running Enterprise, if there are any resource groups defined, and which memory-optimized databases are bound to them
-
XTP and buffer pool memory allocations, because In-Memory OLTP can affect on-disk workloads
-
summary of memory used by XTP
There’s a lot of useful information you can get out of this procedure. Click through for the full documentation.