FIX: Bad query plan created on secondary replicas after statistics updated via FULLSCAN option on primary replica in SQL Server 2012 or 2014

Applies to: SQL Server 2012 EnterpriseSQL Server 2012 DeveloperSQL Server 2012 Enterprise Core


Assume that you use Microsoft SQL Server 2012 or 2014 Always On Availability Groups. After statistics are updated by using the FULLSCAN option on the primary replica, the statistics on the secondary replica become stale or out-of-date. When you run a query on the secondary replica, a bad query plan might be used. This causes slow queries.


Cumulative Update Information for SQL Server:

This issue is fixed in the following cumulative updates for SQL Server:

       Cumulative Update 5 for SQL Server 2014 SP2

       Cumulative Update 12 for SQL Server 2014 SP1

       Cumulative Update 8 for SQL Server 2012 Service Pack 3

Service Pack Information for SQL Server 2012:

This issue is fixed in the following service pack for SQL Server:

       Service Pack 4 for SQL Server 2012

For more information about how to obtain the latest service pack, see How to obtain the latest service pack for SQL Server 2012


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


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