Databases Reference
In-Depth Information
analysis. Furthermore, the overhead of collecting PerfMon data is the lowest compared to
the other data collectors.
➤
The maximum i le size and interval at which you want to collect the data samples
➤
Coni guration of the Windows Event Log
collection
The next step is to coni gure the Proi ler trace. This can
be done using the
Instance-specii c Diagnostics
(arrow
7 in Figure 11-5) section of the tool, used for coni guring
database engine/analysis server trace (arrow 6 in Figure 11-5)
and collection of SQLdiag output. Here you can coni gure
a trace for the database engine and SQL Server Analysis
Services instance. Based on the SQL Server version
selected, you will see the Proi ler trace events populated
in the list, which you can coni gure for your data collec-
tion along with the Proi ler trace rollover size. Collection of the SQLdiag diagnostic script can be
enabled or disabled from this section.
FIGURE 11-6
WARNING
Although you can right-click on a Proi ler event and add i lters from
this section, you shouldn't use this option, as the trace i lter will not be honored
when added to the XML coni guration i le.
The last section in the Diag Manager is
Custom Diagnostics
(arrow 5 in Figure 11-5), which
provides a list of pre-built custom collectors that are already available for data collection. In
addition to this, you can extend the data collection, as described in more detail in the section
“Understanding the Custom Diagnostics.” The
Instructions
(arrow 8 in Figure 11-5) tab at the
bottom of the Diag Manager UI provides an explanation of all the Custom Diagnostics options
when you click on them.
NOTE
If you need to coni gure a SQLdiag collection for a RunAs User (RANU)
SQL Server Express instance, refer to the steps provided at
Search WWH ::
Custom Search