Tuesday, February 05, 2013

 

SQL Diagnostic Runner: Version 1.0

Glenn Berry mentioned the runner for his diagnostic scripts I wrote a few weeks ago. He also mentioned it would be nice to have a UI version. I had already written a basic UI when I initially released the command line version. So here it is, warts and all! (along with a minor update to the command line version)

SQLDiagUI.zip

SQLDiagCmd.zip

Comments and feedback welcome.


# posted by Mitch Wheat @ 11:51 am

6 Comments:

Hi Mitch,
Great tool, makes me wish i was more of a programmer. One issue i've found is that name instances don't work due to the file naming convention. hostname,port works though.

By Blogger Unknown, at February 07, 2013 1:48 am  

Hi Mitch,
Great little tool. One issue is named instances don't work due to file path issues. I can get around with hostname,port.

By Blogger Unknown, at February 07, 2013 1:49 am  

Thank you, David. I didn't have a local named instance to test against. No excuses1 I didn't test it. Fixing now...

By Blogger Mitch Wheat, at February 07, 2013 7:10 am  

FYI: I've tried running it on SQL Server 2012 sp1, and there are a few problems.
Great tool otherwise.
Best regards,
Henrik

By Blogger Henrik Staun Poulsen, at February 13, 2013 6:02 pm  

@Henrik Staun Poulsen: What errors do you receive? What doesn't work? have you tried running the TSQL script directly in SSMS?

By Blogger Mitch Wheat, at February 13, 2013 11:21 pm  

I have uploaded a rebuilt copy of both the command line and UI runner (version 1.0.2.13045). Just tested against a local 2012 named instance with the latest version of Glenn's 2012 script. Worked Fine. Just in process of applying SP1 to 2012 ....

By Blogger Mitch Wheat, at February 14, 2013 10:41 am  

Post a Comment



<< Home
    

Powered by Blogger