sys.trace_events lists available SQL trace events rather than only default-trace collection. Readers asked after my creation-date article.
When a Table Was Created: Find It With Metadata and Traces
To find when a table was created, read create_date from sys.tables. This post adds the default trace and an Extended Events session for the question of who created it, and tests what a rename or an ALTER does to the date.
SQL SERVER – SQL Server Cluster Resource Doesn’t Come Online Randomly
A client’s SQL Server Cluster Resource sometimes failed to come online after a failover to another node. Here is what caused it and how we fixed it.
How to Find Running SQL Trace? – Interview Question of the Week #123
Question: How to Find Running SQL Trace? Once we know the trace exists, how to stop and delete them?
Schema Change Reports in SQL Server: SQL in Sixty Seconds #078
Schema change reports show which tables, views and indexes were created, altered or dropped recently. The tests here read the default trace behind the SSMS report with T-SQL, show what it misses, and set up an Extended Events session for longer memory.
Replacing Profiler Traces With Extended Events
Replacing Profiler traces with Extended Events starts with the question, a focused event session, and a bounded target that avoids needless load.
Reading the Default Trace
Reading the default trace can reveal recent object and configuration changes while its rolling files still retain the evidence.