Tuesday, August 12, 2008


Posting a (slightly edited) comment from Soni's blog. Because I do want to post something here every day and I don't feel like fooling around. I've got stuff to do.

This ... was my day. My entire day.

My latest true love at work is a whacked bit of enterprise software. The application keeps data in MS SQL Server 2005. I need to extract data from it’s db that the application won’t let me get at in the way I want. It can produce HTML or PDF reports at the click of a button but I can’t script that function and parsing the data in HTML is a PITA anyway.

I want it generated by script in ASCII, bitches. Then I’ll slam it into our documentation wiki. Eighteen times a day if I want to. Because I can.


So I install the sql command line tool. Except that 2005 (unlike 2000) installs in a locked down mode. So I need to run the tool to expose the db to the command line tool ..

Did I come here to drain a swamp .. don’t recall .. wow look at that alligator!

Alligator II
Productivity Monster

The configuration tool is .. not .. installed in the Start menu. It does not appear to be on the server at all. This appears to be a once-in-a-lifetime kinda deal so extraordinary that MS’s technet is silent on the subject.

Well … TechNet says in a distant way .. just run the tool. It’s not there? Oh, g’wan - you’re not looking hard enough.

Meanwhile the work that I had to set aside to tend to this is piling up. And it’s the ‘fun’ work wherein I play with Unix boxes and *nix applications that certainly have their failings but the operating system getting … in … my .. way is not one of them.

UNIX - Server
This is not our server room - but the equipment looks familiar.
blog comments powered by Disqus