Thursday, September 22, 2005

 

Worst Case Scenario

Well, after struggling with a significant database problem for the past two weeks (and seriously believing that my job was on the line), I solved it - with significant help from the folks down the hall who wrote DB2.

I rebuilt some major portions of my database and got performance to LIGHTENING SPEED! An outer join with disjunts across tables. That's fancy DBA talk for worst worst scenario for the optimizer. The query was taking about 3 minutes and I was freaking out. The significant help mentioned above got it down to under a second.

I finished rewriting the code and saved everything. It was only 6 o'clock and I thought how nice it would be to go to home while it's still light outside for a change. Some additional changes kept me at work for a bit longer, but I was feeling pretty good.

This morning, I got a page while I was on the freeway coming into work. The server had died. Sure I have backups, but this sets me back another few days.

I'm currently in the worst case scenario for this project. I have nothing - not even a machine to run it on. I can't imagine what else can go wrong here. I'm getting so frustrated that I can't even see straight. My only consulation is looking at my Active Desktop which is a live camera shot of the Coral Princess. She pulled into Cabo San Lucas this morning around 10:00 am my time.


Comments: Post a Comment

Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?

Locations of visitors to this page