SQL options

What do you use?

I spend a good portion of my days hopping back and forth between SQL Server and Oracle. The built in Studio Management work just fine for me for SQL Server, but I find myself using TOAD for some tasks and PL/SQL Developer for others in Oracle.

This is a much greater debate than Chrome v. Firefox because my precious, precious productivity (aka TIME) is at stake. Looking forward to hearing about what I should really be using. Then again, maybe it's just a Google issue. If I'd just find out how to do the things I use one for in the other, then I could stick to one piece of software.

Then again, sometimes you need a paring knife and sometimes you need a cleaver. Or, in my own experience, sometimes you need buttercream and sometimes only fondant will work. I'll let you decide which is which.

Building bits a-plenty

I spent most of the weekend writing a new module for our team's ticketing system. Visual Studio 2010 makes everything ridiculously easy. I remember hating WYSIWYGs a decade ago, but VS makes creating a fully dynamic ASPX site with SQL back-end nearly drag and drop.

Oh, sure, we still have to add some VB and write the stored procedures, but working on this with my partner has been the most fun we've had in a while. Probably the best part is that we are building something that our (internal) customers have desperately needed for some time.

The trick of this project is that we keep scope creeping. Every time we finish a piece of the system, we discover a new piece that we need. It's half insanely frustrating and half too much fun. But I suppose that's to be expected when you support so many different business models.

And yet somehow I managed to have the baby help me build a raised garden bed. She was so helpful with the measuring tape and even putting our weight into the drill to be sure that the screw is countersunk.
Next weekend is the dirt-filling and the irrigation. I'm looking forward to so much fun in the sun!