Assume that you create an INSTEAD OF trigger that uses inserted or deleted tables in a contained database in Microsoft SQL Server 2012 or SQL Server 2014. Unexpectedly, you may find that the INSTEAD OF trigger uses a different collation than the collation that's used by the contained database.

For example, the contained database uses a case-insensitive collation and the INSTEAD OF trigger uses a case-sensitivity collation.


This issue occurs because the INSTEAD OF trigger does not use the DATABASE_DEFAULT collation for inserted and deleted tables in the contained database.


This issue was first fixed in the following cumulative update for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included in the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Note You can find information about the latest SQL Server builds from Where to find information about the latest SQL Server builds.


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


Learn about the terminology that 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?

Any additional feedback? (Optional)

Thank you for your feedback!