October 9, 2002 at 1:44 pm
I am doing some proof of concept work on implementation of database auditing. So far, I'm headed down this path.....I have started individual traces with the procedures, sp_trace_create, sp_trace_setevent, and the other associated procedures to define and start the individual trace events. These will be scripted such that the auditing events start when the server is started. My challenges are.... Starting individual traces in this way only create trace files that cannot be automatically loaded into a database table (at least I haven't seen how to do that). I want to start traces on multiple servers and consolidate the trace data in a central repository on a dedicated server. First off, am I headed down the right design path or is there a slick way using Profiler to start traces when a server starts? I know that Profiler can write to a database table directly. Is there a way to load my trace files directly into a database table without using Profiler?
October 28, 2002 at 6:31 pm
This was removed by the editor as SPAM
October 29, 2002 at 8:50 am
You can have the traces start be setting a startup procedure and starting them in that procedure.
As far as loading into a table, not sure. Have to check. Whether you can or not, I'd store these locally and then automate some DTS to load them onto a central server.
Steve Jones
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply