MERGE statement treats non-nullable computed columns incorrectly in some scenarios - by TroyK1

Status : 

 


3
0
Sign in
to vote
ID 583719 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 8/5/2010 1:35:38 PM
Access Restriction Public

Description

When executing a MERGE statement where the WHEN NOT MATCHED THEN INSERT branch is exercised, if the target table has a clustered index on an attribute that is not of the ON... clause, and that attribute is being updated, and there is a non-NULLable computed column, an error will incorrectly be raised that you cannot insert the value NULL for that computed column.
Sign in to post a comment.
Posted by Newfangled Old-fashioned Stuff on 4/24/2015 at 8:39 AM
Confirmed to still be a bug in SQL 2008 (SP3) build 5869 (X64), as expected.

Confirmed to still be a bug in SQL 2008 R2 build 4321 (X64).

Confirmed to be FIXED in SQL 2012 build 5522 (X64)

Confirmed to be FIXED in SQL 2014 build 2480 (X64)
Posted by Microsoft on 9/8/2010 at 5:33 PM
This issue will be fixed in the next major release of SQL Server.
Eugene Zabokritski, SQL Engine team.
Posted by Microsoft on 8/27/2010 at 12:33 PM
Hi,
Thanks for reporting the issue. I can reproduce the issue in SQL Server 2008. We will investigate the issue and let you know what we find.

--
Umachandar, SQL Programmability Team