Maintaining SQL Server default trace historical events for analysis and reporting
Posted
on SQL Server Central
See other posts from SQL Server Central
Published on Wed, 30 May 2012 06:00:00 UT
Indexed on
2012/05/30
16:53 UTC
Read the original article
Hit count: 222
I often see questions online where someone wants to find out who started a trace, when tempdb last had an autogrow event, or when the last full backup for master occurred. Since these and other events are captured by the default trace, but the default trace only keeps five 20MB rollover files by default. This means that the event you are after may no longer be there, depending on how long ago it was and how busy your server happens to be. Unfortunately, people often need to find this information well after the fact.
© SQL Server Central or respective owner