Databases Reference
In-Depth Information
➤
Insight into the instance's memory usage
➤
A snapshot of the current values for all the SQL Server PerfMon counters
➤
A snapshot of the SQL Server wait statistics
➤
Status of the sessions and requests active on the SQL Server instance. along
with the associated input buffers
➤
Status of the SQL Server schedulers
Using SQLdiag as a Command-line Application
Before looking at the basics of running a SQLdiag data collection, you should i rst understand the
anatomy of the SQLdiag coni guration i le in order to appropriately coni gure the various data
collectors for capturing diagnostic data. Figure 11-1 shows a screenshot of the key elements in the
SQLDIAG.XML
coni guration i le.
FIGURE 11-1
SQLdiag Confi guration File Key Elements
➤
The full-stop (.) for the
Machine Name
value signii es that the data collection is to be done
from the local machine (i.e., the machine from where the SQLdiag execution was initiated).
➤
The asterisk (*) for the
Instance Name
value specii es that the utility should collect data
from all instances installed on the machine.
➤
The
EventlogCollector
element specii es whether the Windows Event Logs need to be
collected and if so, whether they should be collected when the utility starts up or shuts
down, or both.
➤
The
PerfmonCollector
element specii es whether PerfMon data will be collected, and the
pollinginterval
and
maxfilesize
parameter values dei ne the time interval between two
consecutive samples and the maximum size of the .
blg
PerfMon i le, respectively.
Search WWH ::
Custom Search