Consider the following scenario:

  • You have two tables in a Microsoft SQL Server database, one named Main and the other named Sub.

  • Based on the two tables, you create a cube in a SQL Server 2014 or 2016 Analysis Service multidimensional database.

  • In that Analysis Service database, you create some dimension and fact tables for the Main and Sub tables.

  • You enable Pro-active caching for this database and configure some notifications on the dimension and fact tables.

In this scenario, you find that processing for the different partitions is staged. For example, data insert activity occurs in the Main table first and in the Sub table later. The second partition is processed, but no SQL Server query is sent to get the latest data. This results in stale data.

Note This issue does not occur when the two tables have data that is inserted at the same time.


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

Cumulative Update 7 for SQL Server 2016 RTM

Cumulative Update 4 for SQL Server 2016 SP1

Cumulative Update 5 for SQL Server 2014 Service Pack 2

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were included in the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

latest cumulative updates for SQL Server 2014


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


Learn about the terminology Microsoft uses to describe software updates.

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!