There was a rash of stories last week about assorted web sites not coping with February 29th or leap years in general. You'd think by now this kind of thing would have been sorted out - we did after all see off the Y2K bug and the rules of the Gregorian
calendar are quite well established and have been in use for some time.
Interesting to see then that Microsoft's SQL Server 2008 community technology preview
was brought down by the same leap year bug just 48 hours after Microsoft unveiled it. This in the same week they admitted one
in Exchange 2007. Oops.