In a bit of a bind here, been using SQL DM v 10.1 for some time now with no unexpected noticeable issues.
Recently the SQLdmManagementService.exe service is consuming so much memory and on some occasions the CPU utilization spikes. The only way to get the service's hunger for compute resources is to restart the service
I'm not reporting a bug here but would like to know if anyone has had similar experiences? How did you control / resolve the issue?