Using the Default Trace in SQL Server
I have heard of the default trace in SQL Server. I know it’s on by default, but I don’t know how to use it. What can I do with the default trace?
2025-04-18
I have heard of the default trace in SQL Server. I know it’s on by default, but I don’t know how to use it. What can I do with the default trace?
2025-04-18
We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.
2018-07-17
2,946 reads
If you are running an instance of SQL Server 2005 and above then most likely that instance is running the default trace. This default trace is a canned Profiler server side trace that automatically starts up when SQL Server starts. In this article Greg Larsen explains more about the default trace and shows you how to glean some event information from the trace files created by this background trace process.
2012-04-05
3,916 reads
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
By Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
Comments posted to this topic are about the item Happy Holidays, Let's Do Nerdy...
Comments posted to this topic are about the item UNISTR Escape
Comments posted to this topic are about the item Celebrating Tomorrow
In SQL Server 2025, I run this command:
SELECT UNISTR('*3041*308A*304C\3068 and good night', '*') as "A Classic";
What is returned? (assume the database has an appropriate collation)
A:
B:
C:
See possible answers