We have to log SQL 2005, and the default logging method requires turing on OLE Embedding and XP_Cmdshell.
These 2 methods are against all hardening best practices.
How are people monitoring SQL 2005 databases?
Also we are getting a NULL value in the dbo_nic_aud_trace table for curr_trace_ID. When this happens the logging stops. Anyone know why this value is getting NULL?
Thanks
Tim **bleep**
TIM
The null value should not be stopping collection. Have you opened a case with support?