Wednesday, April 24, 2013

SQL Power Doc Update - Version 1.0.1.0

A quick note to let you know that SQL Power Doc version 1.0.1.0 is now live. This release fixes issues reported since version 1.0, adds 11 new assessment checks, and improves error handling in multiple places. The nitty-gritty details of what's changed are available in the changelog.

You can grab the latest version from the CodePlex project page. If you find it useful please do consider giving it a rating and\or review. And of course if you run into any problems post a description on the discussions page and I'll be happy to help troubleshoot.

Thursday, April 11, 2013

Discover, Diagnose, and Document ALL Your SQL Servers On Your Coffee Break

We all know that we should document our SQL Servers, right? RIGHT?

So let's say you had some time on your hands and decided that today's the day you're going to get it done. You might open SSMS, connect to a server in Object explorer, start clicking around, and copying properties into an Excel spreadsheet. That gets old quick, so you write TSQL to grab information...until you realize that you're going deep down the rabbit hole accounting for all the nuances and new features between versions of SQL Server. If you're adventurous you might crack open your IDE of choice and dig into SMO, but that's another rabbit hole of a different kind, too. Frustrated, you give in and download a trial version of a commercial documentation tool. It works pretty well, except it's taking forever to manually go through every database on every server. A couple hours later you've got a handful of databases documented...but what about server configurations or  details about the Windows OS they're installed on? How do you compare server configurations against each other? Or spot potential configuration problems? And what about those servers you just inherited - or don't even know are out there yet?

Wow, you think to yourself as you head home, this could be someone's full time job just keeping track of all this stuff!

There Is a Better Way: Introducing SQL Power Doc

Starting today, there is a better way. I'm proud to officially announce the release of SQL Power Doc.

Imagine combining the functionality of what Quest's Discovery Wizard for SQL Server, your favorite commercial SQL documentation tool, msinfo32.exe, and Brent Ozar Unlimited's sp_Blitz™ script does into a single standalone tool that you can run against all of your SQL servers at once. That's SQL Power Doc.

Here's a look at what SQL Power Doc does:

Discover

Find SQL Server Services on your network by:

  • Active Directory DNS
  • Subnet Scan
  • Computer Name
Document

Collect comprehensive details about all your SQL Server instances and their underlying Windows OS, including:

  • Service Details For All Installed SQL Sever Services
  • Database Engine
    • Configuration
    • Security
    • Server Objects
    • Databases
      • Configuration
      • Database Objects
      • Service Broker
      • Storage
      • Security
  • SQL Agent
    • Configuration
    • Jobs
    • Alerts
    • Operators
  • Windows OS
    • Machine Information
    • OS Information
    • Software 
Diagnose

SQL Power Doc performs over 100 checks to find hidden problems and performance bottlenecks on your SQL Servers before they turn into major headaches.

SQL Power Doc does all of this using Windows PowerShell and Microsoft Excel. Never touched PowerShell before? Don't worry, I've written a How To Guide for PowerShell Beginners to walk you through every step of the way.

While you're on your coffee break you can put SQL Power Doc to work for you to generate comprehensive, top to bottom documentation of your entire SQL Server environment. This documentation is useful for:

  • Baselines - know what your SQL Server environment looked like last week, last month, etc.
  • Security Audits
  • Licensing Audits
  • Provide a complete look at how your servers are configured without having to grant access
  • Troubleshooting
  • Comparing servers and databases
  • Creating a runbook that you can give to your operations team
  • Planning upgrades - see what hidden features are in use on an instance

One More Thing...

SQL Power Doc isn't limited to just SQL Server - you can also use it to collect an inventory of all the Windows machines on your network. If your IT department is looking for a way to document their Windows machines do them a favor and tell them about SQL Power Doc.

Ready To Get Started?

Now that you know there's a tool that can do the work for you there's no excuse not to document your servers. Head on over to the SQL Power Doc CodePlex site, check out the Requirements and How To Guide, then grab the code to discover, document, and diagnose your SQL Servers today!

Tuesday, April 9, 2013

T-SQL Tuesday #41 - Presenting Opens Doors

This blog post is part of T-SQL Tuesday, a monthly SQL blog party with a rotating host and common topic. This month marks #41, hosted by Bob Pusateri (@SQLBob), and the theme is how I came to love presenting.

Presenting Changed My Life

My story starts in early 2006; I had moved to Orlando to work for a small E-commerce company as a Sr. Production DBA, but I was the DBA's equivalent of the ghost who codes. While I had a nice resume there really wasn't much associated with my name and SQL server that I could show off to people. When I had a problem I searched for the answer on Google. I didn't follow anyone's blog or know any of the big names in the SQL Server world. I had no idea was PASS was all about or that the concept of a user group even existed. As I write this I laugh because I'm reminded that I even searched for logins to SQLServerCentral on BugMeNot because I wanted to remain anonymous.

A coworker of mine at the time told me that a friend of his was looking for people to present to a local group of database people. It sounded like an interesting way to meet other people around town who worked with SQL Server so I accepted and agreed to talk about the new XML features in SQL 2005. A month later I made the one hour trek across town to present to 15 people and as much as I'd like to remember that it was an overwhelming success it was anything but. I rambled. I had 3 slides and spent the rest of the time showing code in SSMS. I went at least 20 minutes over time. I know I lost a few people along the way and probably gave a few wrong answers to questions. By all accounts it was a terrible presentation.

But I survived.

The next day I received an email from the user group leader - one Andy Warren (@sqlandy) - with constructive suggestions on how to improve and an invitation to give the presentation again at this newfangled concept he called SQLSaturday. I accepted, took the suggestions to heart, and felt like a million bucks after I gave a much improved presentation to a full room at SQLSaturday #1. It was a great feeling, so I did it again...and again...and started to find new things to present about. I began attending OPASS and reading blogs (and started this blog, too). I kept at it, and in 2009 I was selected to present a session at the PASS Summit, an honor I had every year until 2012 when I attended the Summit in a different capacity - as a PASS Board member and Director of the SQLSaturday portfolio.

It's been quite a journey, to say the least! Along the way I've learned a metric ton (that's the technical term) about SQL Server and I've met incredible people, many of whom I have become good friends with. What a difference between the 2006 me and who I've become now - in large part because of presenting.

You Never Know Who You Will Influence

It wasn't obvious to me at first but I've come to the realize that one of the most rewarding things about presenting is that you have the opportunity to open doors for people, if ever so slightly. I doubt Kevin Kline had any idea who I was when I sat in a session he gave in Tampa many years ago, or who that guy named Jonathan Kehayias (@SQLPoolBoy) a few seats over from me was. I certainly had no idea who Jonathan was when I gave my XML presentation at SQLSaturday, and it's fun to think now that I was the one who first introduced him to XML-DML in SQL Server.

My point is that you never know if the next great blogger, user group leader, or eventual PASS President is someone you encouraged to give their presentation or someone who attended your session and walked away motivated to do more because of it. It doesn't matter if you're just getting started or you're a veteran speaker - by presenting you're helping yourself and others at the same time. I'll call that a win any day!

Your Turn

If you've ever considered giving a presentation but something's holding you back, consider this a challenge to get over it and submit. There are plenty of PASS chapters who will be happy to put you on their schedule and there's no shortage of SQLSaturdays these days either. Both are great places to start and there are plenty of people in the SQL community who can help you prepare in advance.

I promise, it won't be too painful - but be careful, because you might just walk away wanting to do it again!