Hello Mike,
Unfortunately this is a known CR 779922 caused by the fix on CR 718733.
. I am creating a KBA for it. Will let you know the number once I publish it.
The workaround is to use traceflag 12337
dbcc traceon(12337)
go
and if necessary create an unique index.
Hope this helps!
Gek