Databases Reference
In-Depth Information
➤
/M machinename
or
machinelist file
— This is a comma-separated list indicating
the machines from which the utility should collect data. This parameter is rarely used, as
remote data collection should be avoided. A machine name provided using this parameter
overrides the machine name value in the coni guration i le.
➤
/Q
— Runs in quiet mode and prevents any prompts
➤
/C
— This specii es the compression option, which can be useful when you are collecting
diagnostic data for long periods of time, especially for the large PerfMon and Proi ler trace
i les.
/C 1
directs SQLdiag to compress the output folder i les using NTFS compression.
➤
/G
— Connectivity checks are skipped when this switch is specii ed, and data collection
is prevented only due to lack of permission or connectivity issues. SQLdiag will not
collect data by default if the user running the utility is not a member of the Windows
Administrators group on the server.
➤
/R
— Registers the utility as a service
➤
/U
— Unregisters the utility as a service
➤
/N
— This parameter dei nes how SQLdiag controls management of the output folder.
/N 2
renames the existing output folder (if present) and instead writes to the output path speci-
i ed. This can be a helpful option when you perform a data collection for a specii c period of
time and the captured data is analyzed later. This scenario requires preservation of the
output folder and not an overwrite of the existing data. The default option is to overwrite.
➤
/A appname
— Provides an application name for the utility and enables the option of
running multiple concurrent data collection executables with different application names.
➤
/T
— Tells SQLdiag to connect to the SQL Server instance using a specii ed protocol
such as TCP, Named Pipes, Local Procedure Call, or Virtual Interface Adapter. Various
environments are secure and only allow connections using a specii c port or protocol.
In such scenarios, this parameter comes to the rescue and facilitates the important data
connection required to collect diagnostic information.
➤
/L
— Specii es running the data collection in continuous mode. This has to be dei ned in
conjunction with either a start time or an end time using the
/B
or
/E
parameters. This
parameter enables collecting data around the clock when you don't know when the problem
will occur or it occurs intermittently. This ensures that SQLdiag collects the data even if
you are not around monitoring the server during the data collection period.
➤
/B
and
/E
— These specify the starting and ending times of the data collection, respectively.
These two parameters can be used together to collect data while troubleshooting an issue
that occurs during a specii c time period. They enable you to schedule your data collection
without being logged onto the server when the issue occurs at inconvenient hours of the day.
The date and time format for these parameters is
YYYYMMDD_HH:MM:SS
and you can even
specify the time using a + sign. For example,
/B +02:00:00
specii es that data collection
should start two hours from the time the command is issued.
➤
/P
— Sets the support folder path. By default, /
P
is set to the folder in which the SQLdiag
executable resides. This folder contains SQLdiag support i les, such as the XML
coni guration i le, Transact-SQL scripts, and other i les that the utility uses during
diagnostics collection.
Search WWH ::
Custom Search