Databases Reference
In-Depth Information
The arrows in Figure 11-5 show the different coni guration options in the UI that enable you to
easily customize your data collection. Some of the coni guration options will be familiar to you from
the “SQLdiag Coni guration File Key Elements” list of this chapter.
Now take a look at what the Diag Manager UI allows you to customize. The i rst task is to select
the platform: x86, x64, or IA64 (arrow 10 in Figure 11-5). Then you can choose the SQL Server
version using the appropriate tabs. SQL Server 7.0 and SQL Server 2000 coni gurations
(arrow 9 in Figure 11-5) are not supported by this tool.
WARNING
If you forget to select the platform or the SQL Server version and
need to make a change later or post the customizations made, you will lose any
changes made and the options will default to the template selected.
Now that you know how to select the right platform and SQL Server version, consider some key
areas in the tool. The
Issue Type
section (arrow 3 in Figure 11-5) available in the leftmost pane of
the UI is the list of templates you can use for coni guring the data collection, with some events and
collectors pre-coni gured. You could start with the
sql_default_2008
collector and edit them as
appropriate for your data collection needs.
The
Connection Info
(arrow 1 in Figure 11-5) box is where you provide the machine name and the
SQL Server instance name from which you intend to collect the diagnostic data. The full-stop (.) and
asterisk (*) for the machine name and instance name, respectively, direct the coni gured SQLdiag
package to collect data from all the SQL Server instances installed on the local machine. The best
coni guration practice here is to always provide a machine name and an instance name. The
considerations mentioned in the section “Coni guring and Running SQLdiag on a Failover
Cluster” for coni guring SQLdiag on a cluster apply here as well.
After providing the machine name and instance name, you can select the authentication used to per-
mit collection of the data, Windows or SQL Server authentication. If you choose SQL Server authen-
tication, you can only provide the username (arrow 2 in Figure 11-5). You will be prompted for the
password at runtime. The
##SQLDIAG.log
i le will contain the following information when you use
SQL Server authentication for logging into the SQL Server instance:
Password:
User prompted for password at runtime
SQLDIAG Initialization starting...
The next section is
Machine-wide Diagnostics
(see Figure 11-6 and arrow 4 in Figure 11-5), which
enables you to coni gure the PerfMon data collection by specifying the following:
➤
The different PerfMon counters (arrow 4 in Figure 11-5) that you want to collect
— By
default, a set of counters is pre-populated based on the information present in the selected
template. You can enable additional counters that you deem necessary for analyzing your
problem scenario. It is always a good practice to collect all the SQL Server Performance
Monitor counters so that you do not miss any relevant information required for your data
Search WWH ::
Custom Search