FIX: The INSTEAD OF trigger uses a different collation than the contained database uses in SQL Server 2012 or SQL Server 2014

Symptoms
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.
Cause
This issue occurs because the INSTEAD OF trigger does not use the DATABASE_DEFAULT collation for inserted and deleted tables in the contained database.
Resolution
This issue was first fixed in the following cumulative update for SQL Server:


Recommendation: Install the latest 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.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3123089 - Last Review: 05/31/2016 07:07:00 - Revision: 7.0

Microsoft SQL Server 2012 Service Pack 2, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2014 Service Pack 1

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3123089
Feedback