FIX: Prolonged non-transactional usage of FileTable without instance restart may cause non-yielding scheduler error or server crash in SQL Server 2014, 2016 and 2017

Applies to: Microsoft SQL Server 2014 Service Pack 2SQL Server 2014 DeveloperSQL Server 2014 Enterprise


Assume that FileTable isused by File I/O APIs in a high traffic condition for a very long time without instancerestart. In this scenario, you may encounter a non-yielding scheduler error, 100 percent CPU usage, or a server crash. This problem occurs when a user request hits an infinite loop internally.


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:


Learn about the terminology that Microsoft uses to describe software updates.