Limiting Trace File and Table Sizes
SQL Trace results vary in size depending on the event classes that are included in the trace and the way in which the Database Engine is used. If you trace event classes that occur frequently, you can minimize the amount of data that the trace collects by setting the maximum file size or the maximum number of rows. By specifying the maximum file size or rows, you ensure that the trace file or table will not grow beyond the specified limit.
|If you save trace data to a file that already exists, you can append data to the file or overwrite the file. If you choose to append data to the file, and the trace file already meets or exceeds the specified maximum file size, you are notified and given the opportunity either to increase the maximum file size or specify a new file. The same is true for trace tables.|
A trace that has a maximum file size stops saving trace information to the file after the maximum file size has been reached. This option allows you to group events into smaller, more manageable files. In addition, limiting file size makes it safer to run unattended traces, because the trace stops when the maximum file size is reached. You can set the maximum file size for traces created by means of Transact-SQL stored procedures or by using SQL Server Profiler.
There is an upper limit of 1 gigabyte (GB) for the maximum file size option. The default maximum file size is 5 megabytes (MB).
Enabling File Rollover
The file rollover option causes SQL Server to close the current file and create a new file when the maximum file size is reached. The new file has the same name as the previous file, but an integer is appended to the name to indicate its sequence. For example, if the original trace file is named filename_1.trc, the next trace file is filename_2.trc, and so on. If the name assigned to a new rollover file is already used by an existing file, the existing file is overwritten unless it is read only. The file rollover option is enabled by default when you are saving trace data to a file.
|With the file rollover option on, the trace continues until it is stopped by some other means. To stop the trace after you have reached the file size limit, disable the file rollover option.|
A trace with a maximum number of rows stops saving trace information to a table after the maximum number of rows has been reached. Each event constitutes one row, so this parameter sets a limit on the number of events that are gathered. Setting the maximum number of rows makes it easier to run unattended traces. For example, if you need to start a trace that saves trace data to a table, but you want to stop the trace if the table becomes too large, you can do so automatically.
When the maximum number of rows is specified and the maximum number of rows has been reached, the trace continues to run while SQL Server Profiler is running, but the trace information is no longer recorded. SQL Server Profiler continues to display the trace results until the trace stops.