tailieunhanh - Microsoft SQL Server 2008 R2 Unleashed- P21

Microsoft SQL Server 2008 R2 Unleashed- P21:SQL Server 2005 provided a number of significant new features and enhancements over what was available in SQL Server 2000. This is not too surprising considering there was a five-year gap between these major SQL Server 2008 is not as much of a quantum leap forward from SQL Server 2005 | 154 CHAPTER 6 SQL Server Profiler 1 3 20 1 4 NULL 1 5 1 2 1 0 2 2 c trace 2 3 5 2 4 NULL 2 5 1 select from fn_Trace_getfilterinfo 2 columnid logical_operator comparison_operator value 3 10 10 0 0 6 0 7 Profiler 0 7 SQLAgent NOTE You may be wondering why there is always a traceid with a value of 1 running when you run the fn_trace_getinfo procedure. This is the default trace that SQL Server automatically initiates when it starts. The default trace is enabled by default. You can identify which trace is the default by selecting from the catalog view and examining the is_default column. The default trace captures a number of different types of events including object creates and drops errors memory and disk changes security changes and more. You can disable this default trace but it is generally lightweight and should be left enabled. The output from the functions that return trace information is relatively cryptic because many of the values returned are numeric. For example the property values returned by fn_trace_getinfo are specified as integer IDs. Table describes of each of these property IDs. TABLE Description of Trace Property ID Values Property ID Description 1 Trace options specified in sp_trace_create 2 Trace filename 3 Maximum size of trace file in MB 4 Date and time the trace will be stopped 5 Current trace status Download from Defining Server-Side Traces 155 Stopping Server-Side Traces It is important to keep track of the traces you have running and to ensure that heavy traces are stopped. Heavy traces are typically traces that capture a lot of events and are run on a busy SQL Server. These traces can affect the overall performance of your SQL Server machine and write a large amount of information to the trace output file. If you specified a stop time when you started the trace it automatically stops and closes when the stop time is reached. For example in the SQL script in Listing if you wanted the .