SQL Server Trace (Trace)--system trace log; from a small white to a great master, the article is full of details, and the details are outrageous.

Written in front of the words:

Much of this article is an excerpt 

https://www.cnblogs.com/zhijianliutang/p/4113911.html

The author just added some details encountered in the process of practice on the basis of the article;

Again, I would like to thank the author for his selfless sharing

foreword 


If default trace information is turned on, it will automatically record SQL Server startup information when SQL Server starts. This function is like the black box of an airplane, and it will record all changes to the configuration information of a SQL Server instance. Looking at this information, you can see what changes were made to the database at the time of the failure. The default trace information and ERRORLOG are stored in the same log folder with a name such as "log_xxx.trc", where xxx is a set of sequence numbers. You can use Profiler to open these files to view event records, or use the function "fn_trace_gettable" to process these files.

"Tracking" is also ubiquitous in our SQL Server database. If we make good use of tracking techniques, we can conduct directional analysis for certain specific scenarios and find sufficient evidence to solve the case.

Just a few application scenarios:

exist

Guess you like

Origin blog.csdn.net/cplvfx/article/details/129710394