That explains why you're getting the error.

In HHH-11642 Resolved I fixed the fact that when using the legacy dialect on newer/modern SQL Server platforms you get this particular error. One thing you could try is rather than using org.hibernate.dialect.SQLServerDialect, actually specify the SQLServer2008Dialect instead and see if that solves the problem. The fix in HHH-11642 Resolved makes the legacy dialect compatible with the modern dialects but that is part of the next 5.2 maintenance release.