Assume that you run a batch mode query with multiple joins in SQL Server 2017 or 2019. Because of a long recursive call on all the joins present in the query, a Non-yielding scheduler condition may occur.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: