• Has this been resolved? We are having the same issue on two different SQL instances... We are using SQL Server 2014