We had a similar problem when we upgraded to GP2010. We had a custom trigger (from v8 onward) that fired when SOP10200 was INSERTed or UPDATEd. In GP2010, microsoft added the time stamping trigger to update DEX_ROW_TS in SOP10200. When we tested adding a line to an order, the line was INSERTed into SOP10200. The custom trigger would fire and UPDATE SOP10200, the zDT_SOP10200U would fire and UPDATE SOP10200, the custom trigger would fire, the zDT_SOP10200U would fire.......SOP10200 would appear locked and soon the SQL server would lock as well. Before disabling the trigger, why not check and see if there is a custom trigger and see what it does. We fixed our problem by having the custom trigger see if the only UPDATE was the DEX_ROW_TS column and stop firing if it was. Remember when your client upgrades the 'zDT_SOP10200U' trigger will be enabled again.
The zDT_SOP10200U simply updates DEX_ROW_TS with the server's UTC time. I can't think of any issues if you do disable it.
Tim