Consider the following scenario:
- You enable the AlwaysOn Availability Groups feature in Microsoft SQL Server 2014.
- The AlwaysOn database has common language runtime (CLR) user-defined data type (UDT). Additionally, the same CLR UDT exists in more than one database.
- You run a query that involves multiple databases that have the CLR UDT.
2015-02-17 13:07:36.85 spid27s Error: 3449, Severity: 21, State: 1.2015-02-17 13:07:36.85 spid27s SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Snapshot isolation transaction failed in database '<DatabaseName>' 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.
Cumulative Update informationThe issue was first fixed in the following cumulative update of SQL Server.
Update informationTo resolve this issue, apply the update KB 3043788: An on-demand hotfix update package is available for SQL Server 2014 .
Article ID: 3042370 - Last Review: Jun 22, 2015 - Revision: 1