• I saw a fix for something like this in the latest CUs for SQL 2012 & 2012 SP1 (https://support.microsoft.com/en-us/kb/3051993), but it looks like this doesn't cover 2014.