• So, is this a bug in SQL Server itself?

    OK, we'll update and see if the problem persists.