Sql-server – In Memory OLTP causing OOM Issue in SQL Server even though no data in In Memory OLTP Table

If you're sure the user in question has View Server State (and it looks like in your screenshot he does).

Then there are a number of reasons previously put into an msdn blog. Ranging from:

1. Performance Objects and counters set-up during the SQL Server installation failed.
2. A mixture of 64 and 32 bit platforms.
3. Registry permissions have been skewed

To resolve this we can use the same steps outlined in the guidelines for reinstalling the performance counters in a different stack-exchange post:

Using an elevated administrator command prompt perform the following steps.

1. Change the path to the BINN directory of the SQL Server instance you desire to correct.
   (Ex: C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Binn)
2. Execute unlodctr <<REGISTERED SERVER NAME>>
   For example: unlodctr MSSQL$SQL2008 or SQLAgent$SQL2008 ...
3. Execute lodctr /T:<<perf-sql* matching the counters you desire to load>>
   For example: perf-MSSQL$SQL2008sqlctr.ini or perf-SQLAgent$SQL2008sqlagtctr.ini for SQLAgent. The /T is important to load the SQL Server performance counter provider as a trusted provider.
4. Cycle the remote registry service:
   net stop "Remote Registry" then net start "Remote Registry"
5. Force a WMI synchronization using winmgmt /resyncperfctr "<<PID>>"
   where PID is the process id of the WinPriv.exe (you can get this from Task Manager)

The following may also be required:

• Make sure that the correct security permissions have been granted to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009
  registry key:

  1. Grant Full Control permissions to the Creator Owner account.
  2. Grant Full Control permissions to the Administrators account.
  3. Grant Read permissions to the SQL Administrators on that box/Node.
  4. Grant Full Control permissions to the System account

Since you are running Microsoft SQL Server 2014 - 12.0.2000, the very first RTM build including the new Cardinality Estimator I would strongly suggest you try updating to one of the latest CU's.

As stated in this blog post on msdn

You need to apply SP1 but you must also enable trace flag 4199 in order to activate the fix.

SQL Server 2014 Service Pack 1 made various fixes on new Cardinality Estimator (new CE). The release notes also documents the fixes.

You already have TF 4199 active so the improvements should become active automatically.

I would strongly advise you to update and use the new Cardinality Estimator but with all the more recent fixes instead of disabling the new CE alltogheter.

If you still have issues with this single query you can add a plan guide that says OPTION (QUERYTRACEON 9481) for this query alone.