Er, no sorry. Read it just now. OK, so it was a capacity issue unrelated to SQL. Well, that's good news. Unfortunately, thanks to the lightning speed at which mis-information spreads on the internet, this issue will probably be "sticky" for SQL Server for a while.

Regarding the ZDNet blog, I quote:

"Ed Bott is an award-winning technology writer with more than two decades' experience writing for mainstream media outlets and online publications."

Well Ed, the SQLCAT team has posted an official explanation. Where is your official correction on the topic? Award-winning journalists publicly correct their mis-information.