@RogierPronk made the very same suggestion that I was going to make. I've experienced this very problem when we first made the jump from 1012 to 2016. The change occurred in SQL Server 2014.
@RogierPronk made the very same suggestion that I was going to make. I've experienced this very problem when we first made the jump from 1012 to 2016. The change occurred in SQL Server 2014.