0

It seems that Windows Internal Database (MSSQL$MICROSOFT##WID) is causing slow performance on our Windows Server 2012 R2 Remote Desktop Host. It more or less constant using 10-20+% CPU. Users complain their programs are way to slow.

When I stop Windows Internal Database service then it's running fine again.

There are 7 users on the server, with 2 vCPUs, I've already added one to see if that fixed the performance issue, and 4GB RAM. Maybe I should add 1 or 2 GB?

Remote Desktop Connection Broker is using Windows Internal Database so I can't have it closed too long.

Has anyone experienced something similar?

Improve this question
3
  • Baseline investigation please. What exactly is slow? Do not guess, look at the performance counters. How does the hardware look?
    – TomTom
    Nov 14, 2014 at 10:45
  • "Everything". User logon, Outlook, Dynamics, switching program. Hardware is a VMware VM. I'll see if I can get anything from performance counters.
    – kimr-dk
    Nov 14, 2014 at 11:21
  • I've added 2GB RAM, until now there has not been performance issues.
    – kimr-dk
    Nov 17, 2014 at 9:28

1 Answer 1

Reset to default
1

2 vCPUs and only 4 GB of RAM? You're likely just starving your clients of resources. Increase both vCPUs and RAM to give better performance. Increasing to 4 vCPUs will help free up CPU cycles for your clients' processes.

Most likely, you have something installed on the server that utilizes WID (Sharepoint, for one). Dynamics might also use it, but I'm not 100% sure on that one. Either way, splitting the load will help.

Improve this answer
6
  • Most likely, the WID is used by some internal process (like the registry, among other things) - what does this mean? what does the registry use WID for?
    – MDMarra
    Nov 18, 2014 at 3:39
  • @MDMarra Oh, I'm silly and clearly need to sleep. Registry was a bad example (because well, it's not a valid example...). Updating my question...
    – Nathan C
    Nov 18, 2014 at 3:52
  • Remote Desktop Connection Broker is the only thing I can see using WID.
    – kimr-dk
    Nov 18, 2014 at 9:00
  • I had already added an extra vCPU when I saw WID running with 10-20+% CPU, but also the extra RAM seems needed. There have not been any issues since :-)
    – kimr-dk
    Nov 18, 2014 at 15:31
  • @kimr-dk Yeah, that would do it. 4 GB of RAM is pretty low for a shared server. Then again, I have a 2k3 box with ~30 terminal users on 3.2 GB (the 32-bit limit)...
    – Nathan C
    Nov 18, 2014 at 16:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .