SQL Server PowerShell Extensions (SQLPSX) includes a set of function for working with SSIS which among other things allow you…
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:
Find SQL Server Services on your network by:
- Active Directory DNS
- Subnet Scan
- Computer Name
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
- Server Objects
- Database Objects
- Service Broker
- SQL Agent
- Windows OS
- Machine Information
- OS Information
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
- 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!