There’s nothing glamorous about “Low Disk Space” errors.
For some reason the maintenance plan for one of the test db servers wasn’t current. Test servers don’t get monitoring like the production servers, so I’m glad I was checking in. I got to spend about an hour reading up on logs, logical and actual sizes, shrinking, and got in some “wax on, wax off” style practice going through all of our QA and Training dbs.
I also got a release candidate from a vendor that needs to be tested. There’s a limited number of test servers I have access to, but I got it to install and successfully work on a test server also running a previous version. It took a little imagineering, but I installed it, restored a QA database for RC testing [now with lots of space for more transaction logs], upgraded the db to the RC version, and successfully logged in with the new client. All on the first try.
What I’m most satisfied with is that I was able to keep momentum on this task [6 hours thus far] over the course of a Friday & Monday. Friday was also the first workday of 2009. We had a couple of sites close, a few change Third Party plans, some more converted platforms, and one got re-branded entirely. And there are always those pesky bugs that tend to appear at the first of the year. It was enough to fill my day, but I kept plugging along on this release candidate install and if I had let the incidents on Friday utterly consume my day, I couldn’t have made so much progress today. This GTD methodology has something to it.
Let the testing begin.