You may experience slow performance during regular workload when you have a transactional replication publisher set up in Microsoft SQL Server 2012 or SQL Server 2014 and procedures are being replicated. You may also notice that an error message that resembles the following is logged repeatedly in the SQL Server error log when you run maintenance jobs on the server:
time Server * BEGIN STACK DUMP:
datetime Server * datetime spid #
datetime Server *
datetime Server * Non-yielding Scheduler
Additionally, a mini dump file is created.
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:
To work around this problem, stop the transactional replication log reader agent before you run the maintenance jobs.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
See the terminology that Microsoft uses to describe software updates.