The database already crashedPosted: June 18, 2007
The is a zen koan that goes like this:
“One day some people came to the master and asked ‘How can you be happy in a world of such impermanence, where you cannot protect your loved ones from harm, illness and death?’ The master held up a glass and said ‘Someone gave me this glass, and I really like this glass. It holds my water admirably and it glistens in the sunlight. I touch it and it rings! One day the wind may blow it off the shelf, or my elbow may knock it from the table. I know this glass is already broken, so I enjoy it incredibly.'”
Indeed, breakage is inevitable. The database will crash, the datafiles will get corrupted, performance issues will occur and the db team will be blamed for all and any project delays.
Since all these issues are inevitable, and we know from the start that they will occur sooner or later, it is obvious that we need to prepare for them the best we can (remember, a backup plan that is not tested is broken by definition), but there is no reason to be surprised or panic when the inevitable happens, because was bound to happen.
And of course, don’t forget to enjoy the database when it working and appreciate those little moments when surprisingly nothing goes wrong.