Collecting data using batch files.
For SQL 2012 and above, please continue to use the batch file below:
- Go to
Perfstats scripts and download PerfStatsScript.zip to the SQL Server machine that you want to collect data from. Additionally, these batch files are now part of the download when you download SQL Nexus.
- Run StartSQLDiagNoTrace.cmd if you don't want profiler trace, or StartSQLDiagTrace.cmd if you do want to capture a profiler trace. The data will be collected in a subdirectory called SQLDiagOutput
- Collect at least 15 minutes of data during a relevant time period. If the server is fairly idle, you won't see anything interesting in the analysis. If you are trying to identify the root cause of a particular performance issue, you must capture data
that spans one of the problem incidents. Hit CTRL+C once in the SQLDiag console window to stop data collection
- Note: If you call Microsoft support, you may be asked to use a tool called "PSSDiag". SQL Nexus will work with files collected this way, as well.
- Transfer all the output file to the computer where you installed SQL Nexus