Creating a pssdiag package
Creating a pssdiag package means that you use the Pssdiag/SqlDiag manager to configure necessary collectors and package a cab file. Then you extract this cab file on a SQL Server machine to collect data for troubleshooting your SQL Server issues. Creating a
pssdiag package involves the following
- Select a SQL Server version
- Select platform (x86, x64 or IA64)
- Optional customization such as choosing custom collectors, perfmon counters or traces. By default, what was chosen is sufficient for most common needs
- Choose where to save your cab file
Walk-thru: Creating a pssdiag package for 64 bit (x64) SQL Server 2008 R2
Step 1 Launch pssdiag configuration manager
click: Start --> All Programs --> Pssdiag --> "Pssdiag Configuration Manager"
Step 2 Choose SQL Server version
Click on "SQL Server 2008" tab (this is default). See red circle in the screenshot below.
Step 3 Choose platform
Click on the "AMD 64" icon on the left. See the red cicrle in the screenshot below
Step 4 Enter Server and instance name
If you are on a standard (non-cluster) server, you don't have to change "Machine Name" or "Instance Name". Leaving it default will allow collecting data for all SQL Server instances from the machine where you run the package. Optionally,
you can enter the target machine name and SQL Server instance name (if it's default instance, use "mssqlserver") if you just want to collect data for a specific instance.
But for a clustered SQL Server, you must enter "Machine Name" and "Instance Name". See
running pssdiag on a cluster
for additonal instructions.
Step 5 (optional) customize.
You can select or deselect perfmon counters, traces or custom diagnostics. This step is not required as most commonly used diagnostics are already selected for you.
Step 6 Save package
Click on Save button at top left. A diaglog will prompt you where you should save your package
Step 7 SQL Server 2008/R2 Option
If you are configuring the PSSDIAG package using the SQL 2008 tab for data collection on a SQL Server 2008 or SQL Server 208 R2 instance, then you will see an additional option box to choose the appropriate release SQL Server 2008 or SQL Server 2008 R2.
Step 8 Final package
Final dialog will tell you where the final package (.CAB file) is saved.
Step 9 Running the package
Now you can ship this .CAB file to be extracted on the machine which has the SQL Server instance installed from which you want to capture data. See
for more information.