Failed Projects
You start off with the best of intentions, but through raging incompetence, ineptitude or the plain fact that you're working in IT, things go terribly wrong and there's hell to pay. Tell us about the epic failures that have brought big ideas to their knees. Or just blame someone else.
( , Thu 3 Dec 2009, 14:19)
You start off with the best of intentions, but through raging incompetence, ineptitude or the plain fact that you're working in IT, things go terribly wrong and there's hell to pay. Tell us about the epic failures that have brought big ideas to their knees. Or just blame someone else.
( , Thu 3 Dec 2009, 14:19)
« Go Back
Database server upgrade for major client circa 1998
Arrange database downtime for entire weekend at much client annoyance - Check
Off-site client’s huge 19” rack mounted Compaq to workshop - Check
New CPU’s, RAM and HDD’s - Check
3 senior tech engineers in work first thing on Saturday to perform upgrade - Check
Anyone bother to get the admin password from the client - Errrr, shit.
Upgrade fail. Customer lost - Check
( , Thu 3 Dec 2009, 17:41, 1 reply)
Arrange database downtime for entire weekend at much client annoyance - Check
Off-site client’s huge 19” rack mounted Compaq to workshop - Check
New CPU’s, RAM and HDD’s - Check
3 senior tech engineers in work first thing on Saturday to perform upgrade - Check
Anyone bother to get the admin password from the client - Errrr, shit.
Upgrade fail. Customer lost - Check
( , Thu 3 Dec 2009, 17:41, 1 reply)
our dba's
decided to reschedule a previously backed out change. Did they bother telling us? Did they fuck. It's a business critical application used 7 days a week and they took it down at 5pm mountain time (our busiest region).
( , Thu 3 Dec 2009, 19:42, closed)
decided to reschedule a previously backed out change. Did they bother telling us? Did they fuck. It's a business critical application used 7 days a week and they took it down at 5pm mountain time (our busiest region).
( , Thu 3 Dec 2009, 19:42, closed)
« Go Back