This project is read-only.

Project Description
The Central Database Administration project is a combination of a management database for all SQL instances and a central data warehouse for management and monitoring. It uses as much built-in functionality as possible - such as MSX, SSRS, SSIS, etc. Automate at least 1 FTE.


Update Oct 20, 2012

I just wanted to give an update on where the project is going.  As of Aug 30 (build 17181), there has been no further work on the version 1 branch of code.  It continues to be the version that I am using internally at work, but version 2 is the focus of all new development.  That said, what is version 2?

Version 2 is being built using SSDT in Visual Studio 2010.  It is building upon the groundwork laid in version 1, but will be adding a GUI for installing and configuring the MSX environment.  This GUI is being built with WPF in VS2010, and will be deployed as a VSIX - both as a download here and from the Visual Studio gallery.  Hopefully I will be able to provide a VSIX for both VS2010 and VS2012 - we'll see what time allows.

Work has progressed pretty well on version 2.  All database objects will be getting renamed, but it will be automatically performed by the SSDT refactoring capabilities.  (But letting you know in case you've been writing other code to work on top of these procedures.)  The purpose of the renames is to better organize functionality and to better follow our internal naming requirements.

If you look at the source code history you'll notice that there hasn't been any work since Oct 2.  Another higher priority came up at work that has not given me time to get back to this.  But that other priority has actually resulted in a new piece of code that will eventually be migrated into this project.  I had to work on some DTS to SSIS migrations, and hated how much work I actually would be required to do for that endeavor.  So I started instead building a framework for building tables/views/sprocs to take advantage of BULK INSERT to automate the majority of work that was being done inside of the DTS packages.  We might still have SSIS on top of this, but it will be far smaller amount of work.  I'll see how it works out as to integrating into this code base.

Oh, and I also hope to add a data warehouse to the metrics that have been gathering with the existing jobs in the version 1 code.  And from this warehouse some SSRS reports to help us be even lazier at getting to know how our environments are performing and where some work might be needed.

Anyway, thought I would explain what has been happening and where things are going.  And as always, if any of this sounds interesting to you to work on - just get in touch with me and we can talk about how to split things up.


Over the last few years the number of SQL Server instances that I've worked with have only increased, and staffing - well staffing doesn't ever increase; does it? So we do as all "lazy DBAs" do - automate as much of our work as we can. Automate so much that the system does everything that you currently do so you have time to learn how to do better things. And then automate that to learn better things. And of course, don't forget to give the pretty visuals to show your bosses how hard you are working.

The goal of this project is to share as much as possible in a single location in an effort to help other DBAs out there if at all possible. And hopefully in return, if this project helps you any, you will be able to return the favor and help to expand on how much automation this project can do for all of us "lazy DBAs" out here.

Desires from this project:

1. Use as much built-in functionality as possible
2. Must be usable on standard edition and higher
3. Must be usable on SQL Server 2005 and higher for as much as possible, and 2008 and higher where necessary (sorry, CLR is used so 2000 is out)
4. Must be cognizant of security concerns and attempt to minimize security holes as much as possible (ie, no xp_cmdshell, no injection holes, minimal domain access rights)
5. Document code in-line, and provide URL references if code/concepts are borrowed

 

Note:

If you find this utility useful, please consider ratings and/or reviews so that new people finding this will have feedback from others to help judge if this project is worth their time to look at.  Also feedback on desired features or irritations with the project would be helpful to help guide the "next steps."

Thanks for your interest!

Last edited Oct 20, 2012 at 4:12 PM by gephartr, version 8