easyest way is to use sql server profiler.

Create your trace with all filters (db) you want and script it.

Then launch it in a startup job or procedure.

Got that part, but the trace stops almost immediately. Since the job starts the trace-script, should I add the StopTrace and StartTrace procedures?