SQL Nexus Tool

Closed Feature: Realtime Server Status report does not work when connecting to SQL 2008 [19079]

amitban — Thu, 16 May 2013 11:18:23 GMT

Reason: Column cpu_ticks_in_ms of view sys.dm_os_sys_info was replaced with ms_ticks in SQL 2008 and higher.
SQL Nexus Version: 3.0.0.0

Hi,

I researched into this since I used this report frequently for monitoring our servers and kind of fixed it for myself by modifying the Report until seemed to work (although I am not sure if the data being returned now is really correct, someone will still have to verify this).

I am providing my modified version as attachment. Tested with SQL 2005 and 2008 R2.
I'd be happy if my modifications turn out to be correct and if they would make it into a future SQL Nexus release.

Regards,
Marc

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 Post: SQL 2012 PerfWaitStats

eh3034 — Fri, 29 Mar 2013 18:13:24 GMT

Are there any plans to get the PerfWaitStats scripts page updated to include SQL 2012? PerfWaitStats traces are incredibly useful, and it would be great if a working 2012 script could be posted at http://sqlnexus.codeplex.com/wiki/PageInfo?title=Sql2005PerfStatsScript.

New Post: Tables not created for bottleneck rpts

tiermark — Mon, 18 Mar 2013 14:55:44 GMT

Hi Folks,

As mentioned by a number of folks here, some of the reports like the bottleneck report rely of tables not always created when importing occurs. In my environment this seems due to invalid creation of the nnnn_Startup.OUT file. That file seems to be created by running RDTSTestLoop.cmd in the Perf Stats Script for SQL Server 2008R2. Where does that script come from? I do not have it although I have all of the prereq's for running SQL Nexus. If someone could tell me how to replicate the data that should be in the nnnStartup.OUT file that would also be welcome.

It's almost like a secret to determine where some of this stuff comes from. Any help would be appreciated.

Mark

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 Post: Please release the 2012 SQL Nexus and 2012 RML utilities and 2012 PSSDIag

CesarOsorio — Tue, 19 Feb 2013 18:59:46 GMT

yep, when will be the next version released? I need to monitor a 2012 instance and at least you could release the ".cmd".

New Post: Please release the 2012 SQL Nexus and 2012 RML utilities and 2012 PSSDIag

JamieChicago — Fri, 04 Jan 2013 19:15:01 GMT

I need to do analysis on a 2012 instance.

Thanks.

Reviewed: SQL Nexus 3.0.0.0 release (Dec 19, 2012)

dvdvon56 — Wed, 19 Dec 2012 19:33:27 GMT

Rated 1 Stars (out of 5) - Broken links. No clue how to get to batch files referenced. 2008 R2?...where? Looks like the folks who built Windows 8 broke their teeth on this travesty.

New Post: Could not find stored procedure 'ReadTrace.spReporter_BatchAggScaleFactor'

chrismouk — Thu, 18 Oct 2012 15:04:37 GMT

I get the following error when attempting to view the ReadTrace_Main report:

Could not find stored procedure 'ReadTrace.spReporter_BatchAggScaleFactor'

I am using RML 9.01.0109 built for x64

SQLNexus 3.0.0.0 with SQLServer 2008 R2

The only stored procedure I have are name ReadTrace.usp.*

Any hint on how to get this missing stored procedure ?

Thanks

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

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 Post: How to Schedule PerfStats Collection?

dbwagoner — Fri, 24 Aug 2012 14:38:20 GMT

Nevermind...I found that I can use the begin (/B) and end (/E) options in SQLDiag to run this at a scheduled time and that works for me!

New Post: How to Schedule PerfStats Collection?

dbwagoner — Fri, 24 Aug 2012 14:04:43 GMT

I want to schedule a PerfStats collection to run from 3-5 AM using SQL Server Agent (preferably) or Windows Scheduler.

I created an Agent job with the OS commands and the job runs succsessfully, but the trace never starts and the Output folder is not generated. Here are the commands I used (these work when executed manually at the command prompt):

set SQLDIAGCMD="C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLdiag.exe"
"C:\PerfStats_SQLServer2005\StartSQLDiagDetailed_Trace.cmd"

Has anyone successfully scheduled a PerfStats collection? Were you able to schedule the CNTRL-C break at the end of collection?

Thank you!

New Post: Status of the Project

rbellamy — Wed, 08 Aug 2012 00:01:00 GMT

Is this project still under development? I'm curious in particular because there's been no movement in the code repository in three years, and I hesitate to pull the source and start fixing what I find, when there may be a branch in the pipeline I can't see.

I can see that amitban is still moving around here... hopefully this will catch his eye.

Created Issue: RealTime - Server Status - Exception [23139]

rbellamy — Tue, 07 Aug 2012 23:42:37 GMT

See attached screenshots.

Commented Issue: Blocking and Wait Statistics/Bottleneck Analysis Reports [11682]

rbellamy — Tue, 07 Aug 2012 23:40:10 GMT

When I tried to run these 2 reports I get an error that 'The database doesn't have necessary data to run the report'. I later discovered that this is due to the fact that the collation set of the server I loaded the sqldiag data on was case sensitive. When I loaded this data onto a server where the server collation set was case insensitive, these reports started working flawlessly.
Comments: ** Comment from web user: rbellamy **

So, three years later?