New SQL Server community tool

Daniel Janik, 2016-07-05

For those of us in the US, it’s our day of independence. A day that stands for FREEDOM and happiness. Fireworks will light up the sky tonight! For the rest of the world it’s another random day in July. But don’t worry everyone can celebrate “Free”dom with this new community tool.

I’ve spent the last couple years writing, improving, and using this tool at my customers. This health check now has more than 300 data points and even pulls out bad practice and concerns from your procs. As of today, I gift it to the community. #SQLFAMILY


Where to find the tool:

Navigate to www.SQLDATAPROS.COM and click the download free button. Note that there is no registration. If you’d like to send me your email, please feel free. You can also follow me on Twitter at @SQLSME or find me on LinkedIn. A link to my profile is on my blog at


This will take you to my dropbox where you will need to click the download button.

If you don’t have a dropbox account, you can click the “No thanks, continue” button on the bottom to bypass signup.




That’s it! It’s that simple. The only other thing you need to worry about is having .NET 4.5 or higher and possibly the ReportViewer 2015 files. There is no install for this. If you don’t want it anymore, simply delete the files.

You can also get the ReportViewer (2015) and SQLCLRTypes prerequisites from the application zip file on DropBox. This should make finding the items easier since they will be in the zip in a prereq folder. Be sure to install them to allow the tool to run.


How do I use this thing?

Unzip the files to any directory you like. After that, simply open the FitDB application.

Once the application is open, type an instance name into the instance box and then click Test Connection.


Once the connection is successful, the databases list will be populated. Deselect any databases you want to ignore.

Next right click a category on the right and click “Collect Data”.


After you’ve collected data, click the “Reporting” button to view any issues that were found.

If you get an error about “Microsoft.ReportViewer.Common” then you don’t have the Report Viewer 2012 installed. Be sure to grab it from the link referenced above.


Drill into the bar chart or click “View All Data” to get a detailed explanation of each issue.



Please be kind and remember this is being released for the first time and is a BETA.:)


I wish everyone in the #SQLFamily a happy 4th!



  • Fixed a crash on launch from non-USA date formatting
  • Corrected blog post link to ReportViewer.2015 from RV 2012. The application uses 2015, not 2012.





Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.

Robert Davis


1,567 reads

Networking – Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I’d like to talk about social networking. We’ll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let…

Andy Warren


1,530 reads

Speaking at Community Events – More Thoughts

Last week I posted Speaking at Community Events – Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I’ve got a few more thoughts on the topic this week, and I look forward to your comments.

Andy Warren


360 reads