The author spends quite some time explaining that MS SQL Server's CSV is mangled and broken, and what you've said is that it exports CSV. So what does your comment contribute, except to say that you didn't read the article?
that's a deliberately obtuse response formed by avoiding reading the 478 words of supporting detail immediately following. Certainly there exist csvs mssql will import. But I've run into problems with nested quoting, commas inside fields, and unicode. I'm apparently far from the only one. So I think it's hardly hyperbole to say mssql doesn't support csv.
Yeah, me too. The author points this out painstakingly too. I'm not familiar with MS SQL CSV exporting so I can't verify the truth of that statement though.