Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Selective XML index becomes primary after you apply the snapshot in transactional replication in SQL Server 2012

Selective XML index becomes primary after you apply the snapshot in transactional replication in SQL Server 2012

View products that this article applies to.

Symptoms

Assume that you have a table with a XML selective index in Microsoft SQL Server 2012. In this situation, when the table is replicated, this index is created at destination by the snapshot as a Primary XML index, not a Selective XML index.

Note The option to copy the XML indexes is set in the replication article.

↑ Back to the top

Workaround

To work around this issue, do not copy the XML index in the replication and instead create this index as a post snapshot script.

↑ Back to the top

Status

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

↑ Back to the top

Keywords: kb, kbexpertisebeginner, kbtshoot, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2985517
Revision : 3
Created on : 11/20/2019
Published on : 11/20/2019
Exists online : False
Views : 302