This trace was collected on SQL Server 2005 RTM or SP1, where the EventSequence column was 32 bit instead of 64 bit. If the EventSequence column overflows, the replay of events may be in a different order than the order in which they were captured. We strongly recommend that you examine the input trace data and re-assign the EventSequence column if there is overflow, or capture the trace against a server running SQL Server 2005 SP2 or later.
This template tracks connection activity for a server. Normal connection activity is tracked using the login and logout events, ...
This template tracks internal and external wait statistics for individual query statements, batches and RPCs. This template ...
This timer job triggers the background processing operations for the SQL Server Reporting Services Service Application it ...
This tool detects the patterns that predict a specific value (the Target) of a column based on values in the other columns. ...
This trace was collected on SQL Server 2005 RTM or SP1, where the EventSequence column was 32 bit instead of 64 bit. If the ...
This type of Collection does not support changes to its SourceCollection from a thread different from the Dispatcher thread. ...
This Variables collection has already been unlocked. The Unlock method is called only once on a dispensed Variables collection. ...
This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible. ...
This version is not compatible with a later installed version. For more information, see the compatibility information at ...