I am been storing information on the whereabouts of nuclear reactor fuel in this app, but recently we have become aware of the possibility that the information we think we are saving isn't what's getting out. So now we cant be sure some of our uranium hasn't been stolen. Oh well, what's someone going to do with uranium anyway? I suppose it's no big deal."
Grim as that was, it's worth noting it's referring to issues with SQL Server 6.5 and 7 over 10 years ago. As the current release is v10.5 (2008R2) and we're scheduled to next year see v11 (2012) I would suspect the relevant problem tickets have been resolved...
"A Bit Buggy but Pretty Good
I am been storing information on the whereabouts of nuclear reactor fuel in this app, but recently we have become aware of the possibility that the information we think we are saving isn't what's getting out. So now we cant be sure some of our uranium hasn't been stolen. Oh well, what's someone going to do with uranium anyway? I suppose it's no big deal."
(http://www.cdi.org/nuclear/nukesoftware.html and noted on other sites. If one is going to come up with reviews, one can also make fun of some real cases, I suppose.)