Our company has a full time trace running to collect audit data needed for SOX Compliance. We recently purchased and install SQLdm and chose this important Instance as one to monitor. It appears that SQLdm is occasionally stopping the running trace and then restarting it. This causes a security alert in the application that analyzes the trace files.
The SQL Log records that the trace is being stopped and start by the process id that SQLdm is configured to use. No other service or function uses this id.
Does anyone know what function in SQLdm would cause this behavior and if it can be configured to not shut down the trace?