Articles

Technical Article

Write custom trace files in TSQL

SQL Server 2005's default trace is great for monitoring system information and for finding out what happened on your server after problems occur. However, there are times when the events that the default captures are not what you need. Here are instructions for how you can create your own trace files in TSQL to catch events on your database machine.

2007-10-08

3,101 reads

Blogs

Advice I Like: Respect

By

“Don’t aim to have others like you; aim to have them respect you.” –...

Blue Sky Programming – The Optimism Trap

By

Many years ago, before I joined Oracle, I was working on a major modernisation...

Setting Up a Mac for Data Engineering and AI Work

By

If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

SQL Server Still Wins

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Still Wins

DBCC CHECKDB Limits I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits I

Visit the forum

Question of the Day

DBCC CHECKDB Limits I

When running DBCC CHECKDB on SQL Server 2025, can I include the Resource Database?

See possible answers