SQL Gumbo is an application that is currently in development.  It is and will be a database monitoring and management tool.  A new twist to the same needs that will empower those who perform the monitoring, alerting, and management of the databases.   Not a canned solution and will not be for everyone.   More of a do-it-yourself solution with some nice management features.

It has been on the back burner since the first of the year.  So here it goes...it is back on the plate :-/

On a personal note, I can't believe I am going to do this.  I've used pretty much the same strategy in some pretty large scale environments for monitoring and managing the databases.  Simple and effective approach.  I can't overly empathize how simple and lightweight it is.  Can I say "stupid easy?"  Nothing more than a 7 line dos cmd file and sql scripts.  Okay, maybe a little more..but still!  Quite a few people are familiar with it and every once in a while I will still get a call about it.  The DBAs at UHG have made some nice High Availability additions.  More than one person suggested I should build a tool...and always said I would.  Learned a lot while building the Script Store utility.  Not necessarily technical in nature either.  A lot about how I plan, my pain points, etc.   I found I am the worst at creating my own requirements.  Made me wonder if I have ADHD (not that there is anything wrong with that) as I would jump around quite a bit.   I'd would get frustrated at times getting simple features to work and other times I would put something in that would seem rather difficult in the blink of an eye.  Also found that using message boards and google searches may not always be the best approach.   I learned to save a lot of time by researching and understanding before looking around.   I have no idea how much time I wasted trying to get a treeview to work by using a search engine.   Would have been a lot easier if I started out understanding the treeview architecture, methods, and properties.

Here is an image from where it was then.  Also where the Script Store utility was born.   I guarantee it won't look like this when completed; the person creating the requirements will get in the way.  The Version Search utility will most likely be the same and the job scheduler interface probably won't change much either.  Unlike the Script Store utility...this one will use a Multiple Document Interface.

 

0
0
0
s2sdefault