At the time of writing, this problem was known to occur across all SQL Server drivers, OpenLink, native, or otherwise. The origin of this problem is believed to be Microsoft.