sqlnexus Wiki & Documentation Rss Feed

New Comment on "GETTING_STARTED"

sgdevaney — Tue, 02 Apr 2013 07:43:17 GMT

The link to the tutorial http://zeollar.cloudapp.net/Session/144 is still broken. Can the owner(s) of the page please correct this.

New Comment on "GETTING_STARTED"

sgdevaney — Tue, 02 Apr 2013 07:41:52 GMT

Link still does not work. Please can you correct it, supply an alternatuve or remove it completely.

New Comment on "Sql2005PerfStatsScript"

Farshid1723 — Fri, 01 Mar 2013 20:39:10 GMT

To download script files, Click Page Info on the navigation bar and go to the File Attachments section . Download the relevant version

New Comment on "GETTING_STARTED"

ReplTalk — Wed, 19 Sep 2012 19:40:13 GMT

http://zeollar.cloudapp.net/Session/144 link is broken.

Updated Wiki: Sql2005PerfStatsScript

amitban — Tue, 11 Sep 2012 13:37:54 GMT

SQL Server 2005/2008 Performance Statistics collection scripts

The attached batch file, TSQL Scripts plus sqldiag configuration file (XML) can be used together with sqldiag.exe (shipped as part of SQL Server 2005 and sql 2008 installation) to collect data for SQL Nexus to analyze. It can collect profiler trace, blocking and DMV output.

Where to download?

Download the PerfStatsScript2005.zip package for sql server 2005, PerfStats2008.zip for sql server 2008 and PerfStatsScript2008R2.zip for SQL Server 2008 R2. To download this file, click on the Page Info link at the top this page and download from File Attachment section (right hand portion of the page).

How to Use it?

Unzip to a local disk on a SQL 2005, 2008 or 2008 R2 machine and run SartSQLDiagTrace.cmd, SartSQLDiagTrace2008.cmd, SartSQLDiagTrace2008R2.cmd or any other batch file depending on what what you need. See Next Section on what to collect.

What will each batch file collect?

All the batch files will collect these:
- Performance scripts by SQL2005PerfStats.sql or SQL2008PerfStats.sql. it will capture DMVs and blocking information to help troubleshoot performance problems blocking, high CPU etc.
- Profiler trace (each batch file will capture different events and StartSQLDiagNoTrace.cmd doesn't capture any trace)
- Perfmon
- msinfo32
- Windows event logs (system, security and application logs)
Different batch files capture profiler trace events differently. Everything else mentioned in the above section will be captured exactly the same.
- StartSQLDiagTrace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace20082.cmd: they capture general profiler trace events. This is the most commonly used and is sufficient to do initial troubleshoot performance problems.
- StartSQLDiagDetailed_Trace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace2008R2.cmd: They capture detailed profiler trace events. This has slightly higher overhead than general profiler trace events. But it is useful if you want to identify statement level events. For example, you have identified a stored procedure consuming high CPU. not you want to focus on individual statements within that stored procedure.
- StartSQLDiagForReplay.cmd, StartSQLDiagForReplay2008.cmd and StartSQLDiagForReplay2008R2.cmd: They will capture profiler trace events needed for readtrace to do replay. Replay is used if you want to simulate production workload in your test system.
- StartSQLDiagNoTrace.cmd: This one won't capture profiler trace. Since it's not used that often 2008 doesn't have one.

How to customize it?

In general, you don't need to customize it at all. You just run it on the machine that has sql server running. it will discover all instances on that machine or cluster and start collecting data.
If you want to capture for a specific machine or instance, edit " <Machine name="."> and <Instance name="*"" in the corresponding xml. Each batch file has a /I parameter that indicates which XML the batch file uses. for example, if you have a cluster Virtual Server SQLVIR and instance name instance1, you will put <Machine name="SQLVIR"> and <Instance name="instance1" ..... If you have a cluster default instance on virtual server SQLVIR, then you would use <Machine name="SQLVIR"> and <Instance name="MSSQLSERVER"....

Updated Wiki: Sql2005PerfStatsScript

amitban — Tue, 11 Sep 2012 13:37:19 GMT

SQL Server 2005/2008 Performance Statistics collection scripts

Where to download?

Download the PerfStatsScript2005.zip package for sql server 2005, PerfStats2008.zip for sql server 2008 and PerfStatsScript2008R2.zip for SQL Server 2008 R2. To download this file, click on the Page Info link at the top this page and download from "File Attachment" section (right hand column on the page).

How to Use it?

What will each batch file collect?

All the batch files will collect these:
- Performance scripts by SQL2005PerfStats.sql or SQL2008PerfStats.sql. it will capture DMVs and blocking information to help troubleshoot performance problems blocking, high CPU etc.
- Profiler trace (each batch file will capture different events and StartSQLDiagNoTrace.cmd doesn't capture any trace)
- Perfmon
- msinfo32
- Windows event logs (system, security and application logs)
Different batch files capture profiler trace events differently. Everything else mentioned in the above section will be captured exactly the same.
- StartSQLDiagTrace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace20082.cmd: they capture general profiler trace events. This is the most commonly used and is sufficient to do initial troubleshoot performance problems.
- StartSQLDiagDetailed_Trace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace2008R2.cmd: They capture detailed profiler trace events. This has slightly higher overhead than general profiler trace events. But it is useful if you want to identify statement level events. For example, you have identified a stored procedure consuming high CPU. not you want to focus on individual statements within that stored procedure.
- StartSQLDiagForReplay.cmd, StartSQLDiagForReplay2008.cmd and StartSQLDiagForReplay2008R2.cmd: They will capture profiler trace events needed for readtrace to do replay. Replay is used if you want to simulate production workload in your test system.
- StartSQLDiagNoTrace.cmd: This one won't capture profiler trace. Since it's not used that often 2008 doesn't have one.

How to customize it?

In general, you don't need to customize it at all. You just run it on the machine that has sql server running. it will discover all instances on that machine or cluster and start collecting data.
If you want to capture for a specific machine or instance, edit " <Machine name="."> and <Instance name="*"" in the corresponding xml. Each batch file has a /I parameter that indicates which XML the batch file uses. for example, if you have a cluster Virtual Server SQLVIR and instance name instance1, you will put <Machine name="SQLVIR"> and <Instance name="instance1" ..... If you have a cluster default instance on virtual server SQLVIR, then you would use <Machine name="SQLVIR"> and <Instance name="MSSQLSERVER"....

New Comment on "Sql2005PerfStatsScript"

deepaksql — Fri, 13 Jul 2012 10:17:14 GMT

Can any point me the correct link to download the Perfstats script for sql 2008

New Comment on "Sql2005PerfStatsScript"

karabela — Mon, 25 Jun 2012 20:45:33 GMT

when will be the sql2012 perstatscript available?

New Comment on "Sql2005PerfStatsScript"

flyingfdk11 — Mon, 28 May 2012 09:07:33 GMT

Where to download sql server 2005 and PerfStats2008.zip ,this Page Link is lost

New Comment on "ReadTrace"

shbarr — Thu, 26 Apr 2012 16:13:33 GMT

RML Utilities requires Report Viewer 2008 SP1 to run correctly and Report Viewer also has a few updates to be considered. So from what I can tell the installation steps would be as follows: 1. Install Microsoft Report View 2008 SP1 or 2010 ->Microsoft Report Viewer 2008 SP1 Redistributable - http://www.microsoft.com/download/en/details.aspx?id=3841 ->Microsoft Report Viewer 2010 SP1 Redistributable Package - http://www.microsoft.com/download/en/details.aspx?id=6610 2. Install relevant updates for Report Viewer: -> 2008 - Security Update MS09-062 - http://support.microsoft.com/kb/971119 -> 2010 – Hotfixes - http://support.microsoft.com/kb/2549864 3. Install RML Utilities - http://support.microsoft.com/kb/944837 4. Install SQL Nexus

Updated Wiki: Sql2005PerfStatsScript

jackli — Thu, 15 Dec 2011 17:16:59 GMT

SQL Server 2005/2008 Performance Statistics collection scripts

Where to download?

Download the PerfStatsScript2005.zip package for sql server 2005 and PerfStats2008.zip for sql server 2008 and PerfStatsScript2008R2.zip for SQL Server 2008 R2. To download this file, click on the Page Info link at the top this page (alternate link) and download from "File Attachment" section.

How to Use it?

What will each batch file collect?

All the batch files will collect these:
- Performance scripts by SQL2005PerfStats.sql or SQL2008PerfStats.sql. it will capture DMVs and blocking information to help troubleshoot performance problems blocking, high CPU etc.
- Profiler trace (each batch file will capture different events and StartSQLDiagNoTrace.cmd doesn't capture any trace)
- Perfmon
- msinfo32
- Windows event logs (system, security and application logs)
Different batch files capture profiler trace events differently. Everything else mentioned in the above section will be captured exactly the same.
- StartSQLDiagTrace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace20082.cmd: they capture general profiler trace events. This is the most commonly used and is sufficient to do initial troubleshoot performance problems.
- StartSQLDiagDetailed_Trace.cmd, StartSQLDiagTrace2008.cmd and StartSQLDiagTrace2008R2.cmd: They capture detailed profiler trace events. This has slightly higher overhead than general profiler trace events. But it is useful if you want to identify statement level events. For example, you have identified a stored procedure consuming high CPU. not you want to focus on individual statements within that stored procedure.
- StartSQLDiagForReplay.cmd, StartSQLDiagForReplay2008.cmd and StartSQLDiagForReplay2008R2.cmd: They will capture profiler trace events needed for readtrace to do replay. Replay is used if you want to simulate production workload in your test system.
- StartSQLDiagNoTrace.cmd: This one won't capture profiler trace. Since it's not used that often 2008 doesn't have one.

How to customize it?

In general, you don't need to customize it at all. You just run it on the machine that has sql server running. it will discover all instances on that machine or cluster and start collecting data.
If you want to capture for a specific machine or instance, edit " <Machine name="."> and <Instance name="*"" in the corresponding xml. Each batch file has a /I parameter that indicates which XML the batch file uses. for example, if you have a cluster Virtual Server SQLVIR and instance name instance1, you will put <Machine name="SQLVIR"> and <Instance name="instance1" ..... If you have a cluster default instance on virtual server SQLVIR, then you would use <Machine name="SQLVIR"> and <Instance name="MSSQLSERVER"....

New Comment on "GETTING_STARTED"

threesun — Thu, 03 Nov 2011 05:54:04 GMT

alternatively, you can go to this article for guidelines. it is quite useful... http://blogs.msdn.com/b/pamitt/archive/2011/02/25/how-to-use-the-sqldiag-the-sqlnexus-and-the-pal-tools-to-analyze-performance-issues-in-sql-server.aspx?CommentPosted=true#commentmessage

Updated Wiki: collecting data using batch files

jackli — Tue, 24 May 2011 14:56:16 GMT

Collecting data using batch files.

Note that with release of pssdiag/sqldiag manager, these batch files won't be updated. We prefer you use pssdiag/sqldiag manager to collect data.
If still prefers to use these batch files, follow these steps:

Go to Perfstats scripts and download PerfStatsScript.zip to the SQL Server machine that you want to collect data from
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
1. 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

Updated Wiki: collecting data using batch files

jackli — Tue, 24 May 2011 14:55:42 GMT

Collecting data using batch files.

(Note that with release of pssdiag/sqldiag manager, these batch files won't be updated. We prefer you use pssdiag/sqldiag manager to collect data.
If still prefers to use these batch files, follow these steps:

Go to Perfstats scripts and download PerfStatsScript.zip to the SQL Server machine that you want to collect data from
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
1. 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

Updated Wiki: collecting data using batch files

jackli — Tue, 24 May 2011 14:55:01 GMT

Collecting data using batch files.

(Note that with release of pssdiag/sqldiag manager, these batch files won't be updated. We prefer you use pssdiag/sqldiag manager to collect data.

Go to Perfstats scripts and download PerfStatsScript.zip to the SQL Server machine that you want to collect data from
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
1. 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

Updated Wiki: collecting data using batch files

jackli — Tue, 24 May 2011 14:54:36 GMT

Collecting data using batch files.

(Note that with release of pssdiag/sqldiag manager, these batch files won't be updated. We prefer you use pssdiag/sqldiag manager to collect data.

Go to Perfstats scripts and download PerfStatsScript.zip to the SQL Server machine that you want to collect data from
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
1. 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

Updated Wiki: GETTING_STARTED

jackli — Tue, 24 May 2011 14:52:22 GMT

Getting Started

Steps 1-2-3

Install SQL Nexus
Collect perf data from your SQL Server 2005 instance using SQLDiag
Import and analyze the data using SQL Nexus

Installation

following the Installation Steps carefully as it requires certain components

Collecting data

In order to use SQL Nexus, first you will need data collected. SQL Nexus relies on sqldiag.exe collector engine to collect data. But it needs to collect various DMV outputs and specific profiler trace events for the reports to work.
With release of pssdiag/sqldiag manager to codeplex, you have two choices to do data collection.
Method 1 (recommended): Please download pssdiag/sqldiag manager and configuration data collection package to collect data.
Method 2: you can continue to use old method to use bach files provided. collecting data using batch files. But with release of pssdiag/sqldiag manager, we don't intend maintain these batch files.

Analyzing data

Launch sqlnexus.exe and log on to the non-production SQL Server instance where you installed SQL Nexus.
Click on "Import" in the left pane of the main SQL Nexus window.
Provide the file directory where you stored the data collected by SQLDiag. Note: you should provide a directory path, not a file name.
Once the import is finished, you can click on various reports from the left pane of SQL Nexus tool. Start with the "Bottleneck Analysis" report to determine where most query execution time was spent

Tutorials

Here is a quick walkthrough on how to use SQL Nexus to analyze diagnostic data collected using SQL Diag and PSSDIAG: http://zeollar.cloudapp.net/Session/144

Updated Wiki: SQLDiag

jackli — Tue, 24 May 2011 14:45:28 GMT

What is SQLDiag?

In SQL Server 2005, the SQLdiag utility is a general purpose diagnostics collection utility that can be run as a console application or as a service. For more information about sqldiag, please refer to SQL Server books online documentation: http://msdn2.microsoft.com/en-us/library/ms162833.aspx.
Thought default templates are available, shipped products don't have a configuration user interface that would allow you to customize what profiler trace events or perfmon counters to collect. If you want to customize data collection, please use pssdiag/sqldiag manager from codeplex.

Updated Wiki: SQLDiag

jackli — Tue, 24 May 2011 14:45:07 GMT

What is SQLDiag?

Updated Wiki: PSSDiag

jackli — Tue, 24 May 2011 14:41:47 GMT

What is PSSDIAG?

PSSDIAG is a diagnostics utility used to collect profiler trace, perfmon data for SQL Server. PSSDAIG was created to troubleshoot SQL Server 7.0 and 2000 issues. It was evolved and shipped with SQL Server 2005 and beyond. But the shipped product only has a data collector engine called sqldiag.exe. Microsoft Product support continues to maintain a configuration tool that allows engineers to dynamically configure on what to collect. Due to customers' demand, this configuration tool has released under codeplex. please go to Pssdiag/SqlDiag Manager project

If you troubleshoot SQL Server 2000 performance problems, you can continue to use an older version of pssdiag (http://support.microsoft.com/kb/830232)