I believe that is what the other reference was for. Just know the small
trace is not a permanent log, it rolls over.
"David Browne" <davidbaxterbrowne no potted [email protected]> wrote in
message news:uTGN%[email protected]
> "Danijel Novak" <[email protected]> wrote in message
> news:[email protected]
>> You should use profiler in this case. In SQL 2005 there are DDL triggers
>> you could use.
> In 2005 you don't even need DDL triggers. The lightweight always-on trace
> will catch this, and the "Schema Changes History" report in Management
> Studio will show you who did what.
> Now, DDL triggers could be used to capture more details, or actually
> prevent the table from being dropped...