SQL 2008 R2

Mar 18, 2011 at 4:15 PM

Is this site planning on being upgraded to include scripts that work for SQL 2008 R2?  If not does anyone have step by step instructions on how to convert the SQL 2008 scripts to work for R2?

Coordinator
Mar 23, 2011 at 9:19 PM

I am not very sure what you mean by this. Could you please elaborate?

Mar 23, 2011 at 10:28 PM
Edited Mar 23, 2011 at 10:29 PM

When extracting the PerfStatsScript2008.zip folder and running StartSQLDiagTrace2008.cmd on a server with SQL 2008 R2 (as opposed to SQL 2008), the following error occurs:

There are no instances of version 10 on this computer.

This is reproducable in any SQL 2008 R2 environment.

Coordinator
Mar 24, 2011 at 7:27 AM

Is this a cluster or was the SQL instance in question upgraded from SQL 2000/2005 to 2008?

Mar 24, 2011 at 6:09 PM

This is a standard install of SQL 2008 R2, not an upgrade from SQL 2000/2005/2008.  We have reproduced this issue in dozens of SQL 2008 R2 environments.  The script works great in SQL 2008 environments, but does not work in SQL 2008 R2 environments.

Coordinator
Mar 29, 2011 at 5:58 PM

This is not an issue with SQL Nexus. This is because SQLDIAG is not able to connect If you are using Windows Server 2003, then check if this fix has been applied: http://support.microsoft.com/kb/913327

Or if you just have one instance that you need to collect data from, then change the configuration file (.xml) so that the ssver value has "*".

This discussion forum is meant for SQL Nexus related issues. If the above doesn't help, please post your issue on the SQL Server Tools forum on MSDN. Please post back the link here so that I can track it accordingly.

Mar 29, 2011 at 10:59 PM

I thought this was a discussion section for the PerfWaitStats scripts posted at http://sqlnexus.codeplex.com/Wiki/Info.aspx?title=Sql2005PerfStatsScript&action=Info.  Sorry about that.  Do you know who we can talk to about these scripts, as they do not work with SQL 2008 R2?  PSSDiag and SQL Nexus works just fine with SQL 2008 R2, however the issue is with the scripts at the link posted above.  I just clicked the Discussions section next to that URL and it took me here.  Sorry if this is the wrong location.

Coordinator
Mar 29, 2011 at 11:08 PM

Not an issue. I mis-understood the question. I thought it was with PSSSDIAG or SQLDIAG not collecting information. We send that out with the PSSDIAG configurations. I will look into this and post back a public link on this once we have made the script available publicly.

Mar 30, 2011 at 8:45 PM

The current PerfStats XML files for SQL Server 2008 have the version forced to only collect trace data from 2008: <Instance name="*" windowsauth="true" ssver="10" user="">

If you want to collect data for SQL Server 2008 R2 you can change the XML files to: <Instance name="*" windowsauth="true" ssver="10.50" user="">

If you want to collect data for all SQL Server instances regardless of version change the line to: <Instance name="*" windowsauth="true" ssver="*" user="">

Mar 31, 2011 at 3:18 PM

Thanks, that worked great!!!!!  Would it be possible to create a PerfStatsScript2008R2.zip folder on that page with this change?

Coordinator
Mar 31, 2011 at 3:21 PM

Good to know. :)

And yes. I am looking into this and will be posting something along the same lines very soon.