Our organization recently attempted to make a performance optimization by leveraging a column store index. In the process of regression testing, we found that update and delete statements using the ROWLOCK hint were failing due to the Column Store Index. This was a surprise to us, as we have not been able to find any Microsoft documentation that would have led us to believe this is a constraint.
We'd request the constraint be added, so that future users of this great feature are aware before using the index.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ermagana -- Erik, thank you for your feedback.
@MikeRayMSFT -- Mike, please look into this issue.
Thank you @ermagana - I'm reviewing this with product partners & engineers.
@ermagana you mean you hit error 651? That's by design. I'll add a note to docs.
@MikeRayMSFT see PR #16847
Yes, thank you. Can you share a link to the updated docs?
Yes, thank you. Can you share a link to the updated docs?
https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-table