Slow performance or error messages are logged when you have a transactional replication publisher server in SQL Server 2012 or SQL Server 2014

Applies to: SQL Server 2012 DeveloperSQL Server 2012 EnterpriseSQL Server 2012 Standard More

Symptoms


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:

datetime Server * BEGIN STACK DUMP:
datetime Server * datetime spid #
datetime Server *
datetime Server * Non-yielding Scheduler

Additionally, a mini dump file is created.

Resolution


The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 1 for SQL Server 2014

Cumulative Update 7 for SQL Server 2012 SP1

Workaround


To work around this problem, stop the transactional replication log reader agent before you run the maintenance jobs.

Status


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

References


See the terminology that Microsoft uses to describe software updates.