0

Every time we execute SSMS on Windows Server, there is a high disk usage System process for ntuser.dat.LOG, as seem at Resource monitor:

The write rate is between 2 MB/sec and 8 MB/sec.

enter image description here

Why do we have such high disk usage by Windows system process when running SSMS?

  • SSMS version: 11.0.3368.0 (SQL Server 2012 Standard)
  • SQL Server engine: Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) May 22 2013 17:10:44 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.2 (Build 9200: ) (Hypervisor)
  • Operating system: Microsoft Windows 2012 R2 Standard 6.3.9600
  • 3
    Dumb question: Are you running SSMS on your production server? – Erik Darling Feb 9 '18 at 14:30
  • Yes, there is a SSMS on production server just for support team evaluate some things – Junior M Feb 9 '18 at 14:39
  • 2
    That has to deal with the user registry hive, SSMS does look at registry settings, but shouldn't be doing that much changing of the registry. I'd capture a procmon and see what else is going on. – Sean Gallardy Feb 9 '18 at 15:05
  • What should I be looking for? Do I need to use Process monitor to filter by Path looking for NTUSER.DAT.LOG and then what? – Junior M Feb 9 '18 at 19:53
  • Just an overall procmon, then look for when you start SSMS, then look at registry reads/writes after that. If you'd like some help, just start procmon, wait like 3 seconds, open SSMS, then when it finishes opening save the procmon. I can take a look at it at some point and let you know if anything looks odd. – Sean Gallardy Feb 11 '18 at 20:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.