SQL Server is not sensitive to the regional settings.
So MSSQL had nothing to do with the thing
Too bad it is convoluted for me to log a bug (I would have to do it through my national reseller, and then it doesn't feel worth it). I was hoping that someone from the mothership would post in the thread...