Note: This response is only in reference to Rygars post directly above this one]

I ran into this today on a site we inherited and upgraded to 5.1.2. The problem was caused by the DNN360Menu (aka CISS.SideMenu). For some reason, it added what I believe to be an invalid Update trigger on the Tabs table. It is the Subquery defined within the update trigger that is causing the error.

From reviewing the Trigger, I believe it is invalid as it is referencing "Deleted" items. I think the author made a mistake when he copied the Delete trigger and didn't change the Where clause.

I disabled the trigger and re-ran the affected SQL Statements and all is well.

Cathal : I've found out about the DNN360 trigger the hard way as well.  Basically it won't let you do an update to the tabs table that affects more than one tab at a time.  I just got caught out again and found this post.

The syntax to handle the DNN360 triggers is as follows:

disable trigger tabs.DNN360Menu_delete

and then:

enable trigger tabs.DNN360Menu_delete

There are 3 triggeres installed with the dnn360 menu:

DNN360Menu_Insert

DNN360Menu_Update

DNN360Menu_delete

I don't think it's going to be possible to do a blanket detection and disable / removal of triggers in upgrade scripts.  TO make it worse, the disable/enable command is only available in sql 2005.

Note that you need to end the script block with a 'GO' or it will not work correctly.

I think a 'name and shame' policy is better, so that developers feel the pressure to quickly fix their code.