Assume that you have a table that has lots of rows and a full-text index in Microsoft SQL Server 2014. When you try to delete lots of rows from the table in a single transaction, a schema lock occurs as a part of removing the rows from the full-text index, and all the other manipulation queries are blocked by the delete operation.


The issue occurs because, when you delete lots of rows from a very large table with a full-text index, the delete process on the full-text index is performed in a nested transaction. Delete for the full-text index can take longer time even though the delete finishes quickly for the rows in the base table. This reverts all progress of the delete operation on the full-text index if the server is shut down or restarted. It also leads to too much blocking on the base table and lots of transaction locks.

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:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!