asked
snapshot isolation transaction fail in database when tried to select from secondary database
Hi, In my MSSQL Server 2012 AlwaysOn environment, I got some complain about user getting the following error: Snapshot isolation transaction failed in database because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation. I have checked the primary node and their was no relevant DDL change at the time the error occurred. Is there anything else I should check? Thanks, Chun
This query was against a readable secondary, yes? Was there any synchronisation going on at the time of your query?
17 People are following this question.
