Symptoms

Assume that you use AlwaysOn Availability Group (AG) in Microsoft SQL Server. When you execute a query that retrieves data by using non-clustered index seek together with a clustered columnstore index on a secondary replica, the query may take much longer to complete than when it is executed on the primary replica.

Or, assume that you have a non-clustered index on a clustered columnstore index, and Snapshot Isolation level is used. When you execute a query that retrieves data by using non-clustered index seek together with clustered columnstore index key lookup, query execution may also be slow.

Resolution

This fix is included in the following updates:

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017

latest build for SQL Server 2016.

Status

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

References

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!

×