Tips and tips for using SQL event probes

This article will briefly introduce some tips and tips for more effective use of SQL event probes, and hope to help you.

Too many running traces

If the Microsoft SQL server instance runs too slowly, it indicates that the SQL event probe runs too many trails or is running complex trails. Stop any running trace to see if the performance has improved. If stopping a trail improves performance, check the trail carefully to ensure that only necessary information is tracked. Make sure that there are no complex traces running at the same time.

Manage Large tracking files

Large tracking files occupy a large amount of disk space and are very slow and expensive to send over the network. You can delete unnecessary event types and/or data columns and apply filtering to restrict the trail to a specific set of Trace event rules (such as clientprocessid, spid, or application name values ), reduce the size of the saved trace file. Use the same name or new name to save the trail file.

Note: saving the trail file with the same name will overwrite the original file, which will lead to loss of any originally captured events or deleted or filtered data columns.