12 thoughts on “In-Memory OLTP diagnostic script”

1. Pingback: Gathering Information On Memory-Optimized Objects – Curated SQL

2. Ron October 28, 2017 at 11:50 pm

   Great revision on indexing memory-optimized tables. Thank you for posting.

   Reply ↓
3. irving October 30, 2017 at 10:52 pm

   LINE 713 Error: max server memory (MB) instead of max server memory

   Reply ↓
4. Ned Otter Post authorOctober 30, 2017 at 11:24 pm

   Irving,

   Line 713 as written is 100% valid.

   Perhaps your issue is that you don’t have ‘show advanced options’ enabled for sp_configure.

   Reply ↓
5. Konstantin November 13, 2017 at 8:05 pm

   Hi, Ned great thanks for this awesome script. Some problems on case sensitive instance:
   Msg 207, Level 16, State 1, Line 992
   Invalid column name ‘PoolName’.
   Msg 207, Level 16, State 1, Line 992
   Invalid column name ‘DatabaseName’.
   Msg 207, Level 16, State 1, Line 1013
   Invalid column name ‘ClerkTypeUsageMB’.

   I fixed it in my github repo: https://github.com/ktaranov/sqlserver-kit/blob/master/Scripts/In-memory_OLTP_diagnostic_script.sql

   Reply ↓
6. Ned Otter Post authorNovember 13, 2017 at 8:07 pm

   Hi Konstantin,

   Thanks very much for your cdmment, and apologies for the case ‘insensitivity’ of my script. Will fix that in the near future.

   Reply ↓
   1. Konstantin November 13, 2017 at 8:12 pm

      No problem, script is really very useful. I think it is good candidate for sp_blitz_in-memory stored procedure: https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit
      Are you interesting to transform this script to a stored procedure and add it in Brent Ozar team repo? I can help with testing and github move.

      Reply ↓
      1. Ned Otter Post authorNovember 13, 2017 at 8:22 pm

         This script is so new, I think it needs to stabilize a bit before it’s ready for prime time. So let’s be in touch about that possibility in the near future. We can connect on twitter and DM, or you can fill out the contact form on this site with your contact info, and I’ll be in touch.

         Also, there is a survey that I published today about issues blocking wider adoption of In-Memory OLTP. Link here:

         bit.ly/2zUIgAI

         By the way, are you using In-Memory OLTP in production?

         Thanks again for your interest in my script.

         Reply ↓
         1. Ned Otter Post authorNovember 14, 2017 at 4:22 am

            Just updated the script to fix the case sensitive issues.

            Reply ↓
            1. Konstantin November 14, 2017 at 8:54 pm

               Thanks!
         2. Konstantin November 14, 2017 at 8:52 pm

            Take survey and yes, we use In-Memory OLTP in production.

            Reply ↓
            1. Ned Otter Post authorNovember 15, 2017 at 5:04 am

               Thanks — FYI the script was just updated to fix a big in the database loop.