Can you verify that making that change in SQL Server dialects fixes the problem? And maybe even create a PR for it?